...
...
Remote CMS is available with
...
SmartServer 4.
...
4 and higher.
All data is located inside of the Remote CMS Docker container and will be lost during a Remote CMS update because the container will be replaced with new, empty container during the update process. However, the essential data can be configured to remain intact through the update process. For this purpose, directories are mapped to host filesystem as follows:
...
To update the Remote CMS, perform the following steps:
Verify that the docker group exists on the Remote CMS in order to manage Docker as a non-root user using the following command:
Code Block compgen -g
If the docker group exists and your username is part of that group, then you can continue with the following step. If not, then follow the steps (steps #3-6) for creating a docker group in the Install and Start the Remote CMS section. Once your docker group membership changes are in effect, you can continue with the following step.
Stop and remove the Remote CMS Docker container using the following commands:
Code Block docker stop cms docker rm cms
- Download the new Remote CMS image to the host system.
Load the new Remote CMS image into the Docker container using the following command:
Code Block docker load -i <docker_image_file>
- Expose ports 80, 443, and 8883 as needed.
Verify that the path
/home/echelon/backups
exists on the Remote CMS host system before running the Docker container.Run the Docker container using the following command:
Code Block sudo docker run -ddt -e IP_EXTERNAL='<host_name>root.cms' -v postgres:/var/lib/postgresql/12/main -p8883:8883 -p443:443 -p80:80 -p1883:1883 -p8161:8161 --tmpfs /run/lock --tmpfs /run -v /homesys/echelonfs/backupscgroup:/mediasys/sdcardfs/backupscgroup -p8883:8883 -p8443:8443-cgroupns=host --restart unless-stopped --name cms cms/-remote:latest
Start the Remote CMS using the following command:
Code Block docker start cms
...