

Since the appdata and docker-compose.yml are not protected by the SnapRAID. Restart: unless-stopped Backing up the Docker config and compose files env, basically points the docker-compose file to the location of the. APPDATA=/mnt/disk4/appdata/filebotīelow is a sample of a content of the docker-compose.yml for Filebot container. env file to store the variables that I use for my docker-compose.yml. Now, if you noticed in Figure 2 under the docker_compose directory, I have two files which are the docker-compose.yml and.

#!/bin/bashįor i in $(find /mnt/disk13/docker_compose/ -iname docker-compose.yml) This is how I start all the containers manually using a bash script. #!/bin/bashįor i in $(find /mnt/disk4/docker_compose/ -iname docker-compose.yml)

To stop all the containers, I use this bash script. There are instances that I need to stop all the containers. The snippet below how I bring each container up. I have to cd to each /mnt/disk4/docker_compose/ and execute the command docker-compose up -d. Figure 2 Starting and stopping the containers
