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.
You are now ready to start using Sonarr and setup your favorite shows 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. If it didn’t ask for authentication go back to settings->general and make sure authentication is enabled. Now open Sonarr in the new port you chose and it should ask your username + password, login and you will be welcome with the familiar home page for Sonarr. This launches Sonarr in the background in a screen session named sonarr. Now launch it again on the background by executing following command: screen -S sonarr -fa -d -m mono /opt/NzbDrone/NzbDrone.exe Press CTRL+C to stop Sonarr so we can restart it. Once you are done click save, and go back to the SSH screen.
You can set your desired username and password, for the port just choose something random preferrably above number 10 000, but below number 65536. It is very important to set authentication so no one else can access and change the port so it doesn’t conflict with other users on the server. In the settings tab we need to change port and enable authentication in the general tab, like so: Open the address and you will be welcome with this screen, we are now interested in the settings, highlighted with green: You will receive a lot of info notices, after a few seconds it has launched and you may now access it at: or in this example case Execute following command: mono /opt/NzbDrone/NzbDrone.exe Login via SSH to your shell, using something like Putty if you are on windows.
Getting it started is fairly easy! We will eventually include an automatic configurator for it, but for now, here is a easy guide to getting it started and making basic settings! So let’s Setup Sonarr!
Recently we added Sonarr on our seedbox software package.