Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Howto: SABnzbd in docker with portainer.io (Work in Progress) #1599

Closed
sanderjo opened this issue Sep 4, 2020 · 2 comments
Closed

Howto: SABnzbd in docker with portainer.io (Work in Progress) #1599

sanderjo opened this issue Sep 4, 2020 · 2 comments
Labels
Stale Issues automatically closed because they became stale

Comments

@sanderjo
Copy link
Contributor

sanderjo commented Sep 4, 2020

I'm creating a

HOWTO for SABnzbd in docker with portainer.io

Install Docker

Install docker aka docker.io on your Linux. Consult your Linux documentation or docker documentation how to do that.

Make sure you can run it as normal user:

sudo usermod -a -G docker $USER

Fully log out, log in, and make sure you as normal user can

docker ps

which should give

$ docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

meaning docker is running, without any containers

Install portainer

docker volume create portainer_data
docker run -d -p 8000:8000 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce

Check that portainer is running:

$ docker ps
CONTAINER ID        IMAGE                    COMMAND             CREATED             STATUS              PORTS                                            NAMES
567a6d42eae9        portainer/portainer-ce   "/portainer"        4 seconds ago       Up 2 seconds        0.0.0.0:8000->8000/tcp, 0.0.0.0:9000->9000/tcp   portainer

Now go to the webinterface of portainer on http://127.0.0.1:9000/

Fill out a (new) password for portainer's admin account:

image

Click on "Manage local Docker environment" and click on
image

Click on the docker whale:

image

Install basic, non-saving SABnzbd docker

On the left hand side, click on Containers (so http://127.0.0.1:9000/#!/1/docker/containers ) and do this:

image

SABnzbd is now running in docker container:

Make sure SABnzbd is running, with the ports 8080 and 9090 exposed (see arrow on right hand side)

image

You can now access SABnzbd in two ways:

  • click on the exposed port 8080, indicated by the red arrow in the screenshot above
  • http://127.0.0.1:8080/
    Once there, fill out the wizard.

To be done: how to share download stuff to the host ...

Create a SABnzbd containter that does save stuff

On the host, create the directories where the config, inclomplete and complete downloads must be saved:

mkdir sab-docker-config
mkdir sab-docker-incomplete
mkdir sab-docker-downloads

Bind volumes like this

image

Deploy, and fill out SAB's wizard

After filling out the wizard, correct the folder settings like this:

image

Let SABnzbd do a test download. After a succesful download, the result should be like this on the host system:

$ ll sab-docker-downloads/
total 12
drwxrwxr-x  3    911    911 4096 sep  4 22:37 ./
drwxr-xr-x 91 sander sander 4096 sep  4 22:27 ../
drwxr-xr-x  2    911    911 4096 sep  4 22:37 test_download_100MB/

Then, make sure the SABnzbd docker automatically restarts

image

@sanderjo
Copy link
Contributor Author

sanderjo commented Sep 4, 2020

Note: that's a lot of GUI stuff. If you prefer CLI, you can do this:

docker create \
  --name=sabnzbd \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/London \
  -p 8080:8080 \
  -p 9090:9090 \
  -v /path/to/data:/config \
  -v /path/to/downloads:/downloads \
  -v /path/to/incomplete/downloads:/incomplete-downloads `#optional` \
  --restart unless-stopped \
  linuxserver/sabnzbd

For the /path/to/... you have to fill out the directories on the host system.
After that, you can start the container via Portainer, or with docker start.

@stale
Copy link

stale bot commented Sep 25, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale Issues automatically closed because they became stale label Sep 25, 2020
@stale stale bot closed this as completed Oct 2, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Stale Issues automatically closed because they became stale
Projects
None yet
Development

No branches or pull requests

1 participant