Public | Automated Build

Last pushed: a year ago
Short Description
Short description is empty for this repo.
Full Description

Docker Sonarr (previously NzbDrone)

Tags

  • tuxeh/sonarr:latest - Installs from Sonarr master repository
  • tuxeh/sonarr:develop - Installs from Sonarr develop repository

Ports

  • TCP 8989 - Web Interface

Volumes

  • /volumes/config - Sonarr configuration data
  • /volumes/completed - Completed downloads from download client
  • /volumes/media - Sonarr media folder

Docker runs as uid 65534 (nobody on debian, nfsnobody on fedora). When mounting volumes from the host, ensure this uid has the correct permission on the folders.

Running

The quickest way to get it running without integrating with a download client or media server (plex)

sudo docker run --restart always --name sonarr -p 8989:8989 -v /path/to/your/media/folder/:/volumes/media -v /path/to/your/completed/downloads:/volumes/completed tuxeh/sonarr

You can link to the download client's volumes and plex using something similar:

sudo docker run --restart always --name sonarr --volumes-from plex --link plex:plex --volumes-from deluge --link deluge:deluge -p 8989:8989 tuxeh/sonarr

Updating

To update successfully, you must configure Sonarr to use the update script in /sonarr-update.sh. This is configured under Settings > (show advanced) > General > Updates > change Mechanism to Script.

After updating, the update script will stop the container. If the container was run with --restart always, docker will automatically restart Sonarr.

Docker Pull Command
Owner
tuxeh
Source Repository

Comments (9)
bulliteshot
a year ago

This image has a lot of deep issues related to tasks not running after a fair amount of use. There's no helpful info in the trace logs. Anyone else running into this problem, switch to linuxserver/sonarr image

mconnolly05
a year ago

Forgot to mention below - this is on QNAP Container Station

mconnolly05
a year ago

I can't figure out why I keep getting this issue on startup and then when I try to add indexers. I can't add indexers because it can't seem to resolve the host names.

[v2.0.0.4146] System.Net.WebException: Error: NameResolutionFailure
at System.Net.HttpWebRequest.EndGetResponse (IAsyncResult asyncResult) <0x41084680 + 0x001ab> in <filename unknown>:0
at System.Net.HttpWebRequest.GetResponse () <0x4106ff00 + 0x0005a> in <filename unknown>:0
at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.Coo
kieContainer cookies) <0x410769f0 + 0x003cd> in <filename unknown>:0

Any thoughts?

sethbrasile
a year ago

For those having permissions issues: chown -R the folders to be owned by 'nobody' and belong to the 'docker' group.

like: sudo chown -R nobody:docker <dirname>

connorxxl
2 years ago

Same problem here with Synology Docker. I've been able to get Sonarr started when allowing access for everyone on the Sonarr config folder on the Synology (chmod -R 777...). Unfortunately I can't access tv series in the media folder due to these permission issues. transmission and sabnzbd both work fine without any permission quirks... Anyone knows a solution? Thanks a lot!

tscibilia
2 years ago

I'm running this through synology's docker app. when i specify the volumes and mount path for /volumes/config the log always outputs and error and shuts down the container.

"System.UnauthorizedAccessException: Access to the path "/volumes/config/sonarr/nzbdrone.pid" is denied."

i tried chowning the folder I'm using for config to mount to to be owned by "nobody" but that didn't seem to work. Any ideas?

hamiltont
3 years ago

Docker runs as uid 65534 (nobody on debian, nfsnobody on fedora). When mounting volumes from the host, ensure this uid has the correct permission on the folders.

Instead of relying on host permissions, perhaps start.sh should set permissions as needed before calling mono?

keepitshut
3 years ago

any way to setup ssl with sonarr?

coaxial
3 years ago

Thanks!