Installing Connectware on Docker
Last updated
Was this helpful?
Connectware 1.8.0
Last updated
Was this helpful?
You have a .
You have a Internet connection to download Docker images from registry.cybus.io.
Docker and Docker Compose are installed and running on your host.
For more information on installing Docker, refer to the . Docker Desktop includes Docker Compose along with Docker Engine and Docker CLI which are Compose prerequisites.
You are familiar with Docker. For more information on using Docker, see our .
The installer script allows you to quickly install Connectware.
Download the installer script for the Connectware version that you want to install.
Download link for the installer script of the latest Connectware version:
To download the installer script for a specific Connectware version, use the following link and replace <VERSION> with the Connectware version:
For example, to download the installer script for Connectware 1.7.1, use the following link: In the example below, we will use the latest version of Connectware.
Optional: It is a security risk to run bash scripts downloaded directly from the web. So feel free to open the installer script and check its contents.
Make the script executable so it can be run as a script.
You can now run the installer script to install Connectware.
Run the installer script.
The version of Connectware will be printed with a greeting. To confirm that the version is correct, press enter.
You will now be asked for your desired target directory for installation. In this example we will press enter to go with the default path: /opt/connectware
The installer script will then run preflight checks to make sure that all system requirements are met. If they are not then please check the prerequisites section at the beginning of this lesson.
If all requirements are met then you should see the following output.
You will now be prompted for your Cybus license key. If your credentials are valid then you should see the following output.
You will now be asked whether you would like to boot Connectware as a system-service. Without this, the application must be started by hand every time the host system starts. In this example we will press enter to confirm yes.
The installer script will then print your chosen options and ask for confirmation that they are correct. If you followed this example then you should see the following.
The Connectware container images will then pulled onto your system. After they are successfully pulled, the installer script will check for old container images of previous Connectware versions, which can safely be removed („pruned“) to clean up disk space. The installer will ask for confirmation before any container images are removed. In this example the question looks as follows.
After confirming your choice, you can observe the result of the image removal operation. As the last step, the installer will print a message telling you Connectware has been started or which commands you need to enter to run or stop Connectware. In our example you should be prompted with the following.
Running the installer with the -s or --silent flag will start the installation in an automated mode without the need of user interaction.
To use this way of deploying Connectware the license key has to be supplied using the --license-key flag.
This deploys Connectware in a minimal configuration to the default /opt/connectware directory without installing the systemd service.
You can further personalize your installation using the supported installation flags. To see a full list of options just run the installation script with the --help flag.
In case you need to update or change the certificate files (for example if you renewed them using certbot with Let’s Encrypt or want to add a self-signed certificate) you can do this by copying them to Connectware:
The name of your Connectware container depends on the directory it was installed to and is rendered as <your-connectware-directory>_connectware_1. By default Connectware is installed to /opt/connectware/ which results in the container name connectware_connectware_1.
Restart the Connectware proxy to apply the changed files.