|
|
|
|
|
|
|
:bangbang: Please beware that container upgrade needs a restart of the container and will STOP ALL RUNNING PROCESS :bangbang:
|
|
|
|
|
|
|
|
# How to upgrade (one or all containers)
|
|
|
|
|
|
|
|
|
|
|
|
1. Connect to the server as root
|
|
|
|
2. Go to `/home/VNC/` and run `./upgrade-docker-compose.sh <user>`, `<user>` can be either a username (like `test`) or the keyword `all` to upgrade all containers
|
|
|
|
3. Check that all upgraded VNC are running (if you get a password prompt, it is working), you can use `list_instances.sh` to see all the URL to test
|
|
|
|
|
|
|
|
:bangbang: Beware that the stdout will through a couple of "normal" errors :
|
|
|
|
|
|
|
|
`Pulling vnc ... error`
|
|
|
|
|
|
|
|
`ERROR: for vnc pull access denied for vnc, repository does not exist or may require 'docker login'`
|
|
|
|
|
|
|
|
`ERROR: pull access denied for vnc, repository does not exist or may require 'docker login'`
|
|
|
|
|
|
|
|
|
|
|
|
This is due to the fact that the `vnc` image is not in the Docker Hub repositories but in our Gitlab. Therefore, the image pull fails and the image is built right after.
|
|
|
|
|
|
|
|
# Technical details
|
|
|
|
|
|
|
|
The script `/home/VNC/upgrade-docker-compose.sh`, does the following steps:
|
|
|
|
1. Pull last version of the `vnc` source repository
|
|
|
|
2. Pull external docker images
|
|
|
|
3. Build local `vnc` image
|
|
|
|
4. Copy `docker-compose.yml` from source repository to user(s) directory(ies)
|
|
|
|
5. Restart the container(s) |
