lscr.io/linuxserver/sonarr:latest
should retrieve the correct image for your arch, but you can also pull specific arch images via tags./tv
and /downloads
as optional paths, this is because it is the easiest way to get started. While easy to use, it has some drawbacks. Mainly losing the ability to hardlink (TL;DR a way for a file to exist in multiple places on the same file system while only consuming one file worth of space), or atomic move (TL;DR instant file moves, rather than copy+delete) files while processing content.<external>:<internal>
respectively. For example, -p 8080:80
would expose port 80
from inside the container to be accessible from the host's IP on port 8080
outside the container.-p
)8989
-e
)PUID=1000
PGID=1000
TZ=Europe/London
-v
)/config
/tv
/downloads
FILE__
.PASSWORD
based on the contents of the /run/secrets/mysecretpassword
file.-e UMASK=022
setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.-v
flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID
and group PGID
.PUID=1000
and PGID=1000
, to find yours use id user
as below:docker exec -it sonarr /bin/bash
docker logs -f sonarr
docker inspect -f '{{ index .Config.Labels "build_version" }}' sonarr
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/sonarr:latest
UMASK_SET
in favor of UMASK in baseimage, see above for more information.