|
|
# Access a container configuration and persistent data
|
|
|
|
|
|
Users with a VNC container in production have a dedicated `/home/VNC/prod/<username>` folder on the server.
|
|
|
|
|
|
This folder mainly contain the `docker-compose.yml` and `.env` files for a specific user.
|
|
|
Those files describe and configure all the remote desktop environment for a specific user.
|
|
|
|
|
|
Container persistent data is stored in a *Docker named volume*. The name of the volume is self explanatory and contain the user name.
|
|
|
|
|
|
Data on the name volume are accessible in `/var/lib/docker/volumes/<volume_name>/_data/`, **do not write directlry on this directory**
|
|
|
|
|
|
For details on how to list and access Docker volumes from the host, please refer to the [Docker volumes official documentation](https://docs.docker.com/engine/reference/commandline/volume/).
|
|
|
|
|
|
# Restart a container
|
|
|
|
|
|
To restart a user container :
|
|
|
1. Go to the `/home/VNC/prod/<username>` folder on the server
|
|
|
2 Run the following (needs to be in the `docker` group or root priviledges) :
|
|
|
`docker-compose down` (wait for the command to finish, it can take seconds)
|
|
|
`docker-compose up -d`
|
|
|
|
|
|
Container restart should be necessary in two cases only :
|
|
|
1. The container needs to be upgraded
|
|
|
2. The container became irresponsive or crashed
|
|
|
|
|
|
In the second case, please run the following command BEFORE restarting the container, and contact contact@tetras-libre.fr :
|
|
|
```bash
|
|
|
docker-compose logs > lastLogs
|
|
|
``` |