linuxserver-archive / docker-sickbeard

The LinuxServer.io team brings you another container release featuring easy user mapping and community support. Find us for support at:

• forum.linuxserver.io
• IRC on freenode at #linuxserver.io
• Podcast covers everything to do with getting the most from your Linux Server plus a focus on all things Docker and containerisation!

# DEPRECATED, NO LONGER MAINTAINED AND/OR REFRESHED

lsiocommunity/sickbeard

The ultimate PVR application that searches for and manages your TV shows Automatically finds new and old episodes for you and it works with your current download client!. Includes updated python ssl for newer sites like PTP etc.Sickbeard

Usage

docker create --name=sickbeard \
-v <path to data>:/config \
-v <path to downloads>:/downloads \
-v <path to tv-shows>:/tv \
-e PGID=<gid> -e PUID=<uid> \
-e TZ=<timezone> \
-p 8081:8081 \
lsiocommunity/sickbeard

Parameters

The parameters are split into two halves, separated by a colon, the left hand side representing the host and the right the container side. For example with a port -p external:internal - what this shows is the port mapping from internal to external of the container. So -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 http://192.168.x.x:8080 would show you what's running INSIDE the container on port 80.

• -p 8081 - the port(s)
• -v /config - where sickbeard should store its config files etc.
• -v /downloads - your downloads folder
• -v /tv - your tv-shows folder
• -e PGID for GroupID - see below for explanation
• -e PUID for UserID - see below for explanation
• -e TZ for timezone information, eg Europe/London

It is based on alpine linux with s6 overlay, for shell access whilst the container is running do docker exec -it sickbeard /bin/bash.

User / Group Identifiers

Sometimes when using data volumes (-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. Ensure the data volume directory on the host is owned by the same user you specify and it will "just work" ™.

In this instance PUID=1001 and PGID=1001. To find yours use id user as below:

  $ id <dockeruser>
    uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)

Setting up the application

Web interface is at <your-ip>:8081 , set paths for downloads, tv-shows to match docker mappings via the webui.

Info

• To monitor the logs of the container in realtime docker logs -f sickbeard.

• container version number

docker inspect -f '{{ index .Config.Labels "build_version" }}' sickbeard

• image version number

docker inspect -f '{{ index .Config.Labels "build_version" }}' lsiocommunity/sickbeard

Versions

• 21.07.17: Internal git pull instead of at runtime.
• 25.05.17: Rebase to alpine 3.6.
• 14.10.16: Add version layer information.
• 10.09.16: Add layer badges to README.
• 28.08.16: Add badges to README.
• 08.08.16: Rebase to alpine.
• 03.11.15: Initial Release.

docker-sickbeard's Issues

Problem updating Sickrage within Docker on Synology

Not sure if this is a Docker or a Sickrage problem or a Synology problem.
I am running current versions of each, and this has been going on for a while, through multiple versions of each.

Docker 17.05.0-0379
Accessing the Sickrage Web GUI via a Windows 10 computer on the LAN

If I select to update Sickrage from the GUI, Sickrage appears to shutdown and restart with the update satisfactorily.

However, Sickrage doesn't really work at that point with the Sickrage log showing repeated messages:

2018-09-19 07:07:58 INFO MAIN :: Starting SickRage [master] using '/config/config.ini'
2018-09-19 07:07:58 INFO TORNADO :: Starting SickRage on http://0.0.0.0:8081/
2018-09-19 07:07:58 INFO TORNADO :: Could not start webserver on port 8081: already in use!

which repeat ad infinitum.

To get out of this loop, I

• Shut down Sickrage from the web GUI
• Stop Sickrage in Docker on my Synology
• ReStart Sickrage from Docker

Then, everything works OK.

Any thoughts to correct this annoyance would be appreciated.

Sickbeard init script throws error

Starting up Sick Beard master
10:46:40 INFO::MAIN :: Checking database structure...
10:46:40 INFO::MAIN :: Database upgrade required: Initial Schema
10:46:40 ERROR::MAIN :: Your database version (44) has been incremented past what this version of Sick Beard supports (18).
If you have used other forks of Sick Beard, your database may be unusable due to their modifications.

Ubuntu Server 16.04

Thanks, team linuxserver.io

Do not git pull on first run.

The Docker entrypoint script should not be doing a git pull on startup. Docker images should be static precomputed images that are transportable and immutable.

The git pull should be done at the build stage, and then the final product uploaded to Docker hub. With it being done on first run, there is no way to guarantee that the image will work (like I just have, with a DNS failure resulting in a pull failure), and the image is also prone to false starts due to github outages. Once a false start is encountered, the user has no choice but to stop the container, remove the image, and redownload the entire docker image again.

BTN API

Hello,
can you please update Sickbeard so that it's compatible with the latest BTN Api's.
There is already a bufix
midgetspy/Sick-Beard#982

Thank you