lscr.io/linuxserver/sickgear:latest
should retrieve the correct image for your arch, but you can also pull specific arch images via tags.downloads
within this container may be incoming
in other versions.PGID
and PUID
within this container may have been APP_UID
and APP_UID
in other versions.config
within this container may be set as the environmetal variable APP_DATA
in other versions.config.ini
may be configured as a fixed path cache_dir = /data/cache
. Symptoms of this issue include port usage problems and a failure to start the web server log entries. Whilst the container is stopped alter this directive to cache_dir = cache
which will allow SickGear to look for the folder relative to the volume mounted /config
directory.<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
)8081
-e
)PUID=1000
PGID=1000
-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 sickgear /bin/bash
docker logs -f sickgear
docker inspect -f '{{ index .Config.Labels "build_version" }}' sickgear
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/sickgear:latest
UMASK_SET
in favor of UMASK in baseimage, see above for more information.