Configuration of docker-compose.ymlĪfter installing docker Compose and verifying it is working we can create the docker-compose.yml file that contains our containers configuration. Now we can run docker Compose commands with the proper format. Run the test command again but this time like debian: docker-compose -v Reload the shell configuration: source ~/.profile Save and exit,now there should be a hidden file. These options are required for Compose to recognise the docker-compose.yml file we are going to setup later or it will throw errors.Also for the time being it seems that you can not use the -f flag effectively when Compose is installed as a docker image, so commands will have to be run from the directory the docker-compose.yml file resides. portainer, or in our case docker Compose that will in essence claim docker actions for the apps we’ll specify later on.The -v and -w options specifies the temporary host and internal dirs respectively to store and access data. It tells the container to use the unix socket of the docker daemon,something we include in containers that need to do stuff with the docker daemon of our host like monitor/manage docker containers e.g. With this alias every time we execute the command docker-compose a container with the specific options will be run. v /var/run/docker.sock:/var/run/docker.sock \ The shell used by Alpine is ash.We will create an alias specific to the user dockeras by creating a file and adding the following lines in /home/dockeras/ directory: nano ~/.profile echo alias docker-compose="'"'docker run -rm \ Additionaly we use the –rm option which removes the container after running it or else we’ll end up with needless docker containers each time we execute the command. This can become tedious so we will create an alias to make Compose execution similar to the normal installation method. Test that it is working: docker run -rm docker/compose:1.23.2 -vĪs you can see we executed docker Compose using a docker command. On Alpine there is no package for docker Compose and following the official guide for installing on Linux will not work.So we will install docker Compose as a docker container.ĭownload the script: sudo curl -L -fail -o /usr/local/bin/docker-compose Per Ponyo Dogg’s comment the package is now included on Alpine so we can just run: apk add docker-compose Test that it is working: docker-compose -v Install Docker Compose on Alpine The script is downloaded in /usr/local/bin/ and we need to make it executable: sudo chmod x /usr/local/bin/docker-compose Substitute 1.23.2 with the current Compose version, check latest version here and skip the RC versions. In debian installation is straighforward.Download the script: sudo curl -L "$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose The whole process involves installing docker Compose and creating a yaml file that contains the parameters of the containers. Same may apply to other *arr packages (Radarr, Prowlarr, Lidarr, etc.).Continuing from how to install sonarr radarr and jacket with docker, we’ll see how to combine the three services into a docker stack.With docker Compose we will be able to update the docker images and run the respective containers with a single command. qpkg main app folder to prevent this happening (as already implemented after my report listed in the above post). Workaround could be to store the root of Sonarr package in a separate folder inside the. Behavious is similar to what I have reported here for Bazarr: My guess is that updating the app will remove the folder, thus deleting the database and configuration files. If you're on Linux, you will probably have to change the home directory for the user that is running Sonarr and copy the current contents of the ~/.config/Sonarr directory to preserve your database. This means Sonarr will be unable to update itself without risking data-loss. Please look at System => Info to see the current AppData
0 Comments
Leave a Reply. |