Running Usenet Stack as Docker Containers

In Running Usenet Stack on Kubernetes, I covered how to deploy a Usenet stack onto Kubernetes.

Image result for docker container

As it turned out, Kubernetes has won the race as the orchestrator of choice but not everyone is running it in their home lab just yet. I received multiple requests how to translate my YAML files into Docker run commands.

This image has an empty alt attribute; its file name is text256.png

sudo docker run -d –name=radarr -e PUID=1000 -e PGID=1000 -e TZ=America/New_York -p 7878:7878 -v change_me:/config -v change_me:/movies -v change_me:/downloads –restart unless-stopped linuxserver/radarr

The above command will launch a docker container from the linuxserver/radarr image and publish the application on port 7878.
Before you just run the above command, please make sure to change following paths:

/config
stores the configuration files

/movies
location of the downloaded movies after it has been moved from the /downloads folder

/downloads
download folder where your NZBGet or SABnzbd app will store the downloads

sudo docker run -d –name=sonarr -e PUID=1000 -e PGID=1000 -e TZ=America/New_York -p 8989:8989 -v change_me:/config -v change_me:/tv -v change_me:/downloads –restart unless-stopped linuxserver/sonarr

This is basically doing the same as the container for Radarr, except this application will be launched on port 8989. As with Radarr, Sonarr all needs some paths updated before launching the above command:

/config
stores the configuration files

/tv
location of the downloaded tv shows after they have been moved from the /downloads folder

/downloads
download folder where your NZBGet or SABnzbd app will store the downloads

Image result for nzbget

sudo docker run -d –name=nzbget -e PUID=1000 -e PGID=1000 -e TZ=America/New_York -p 6789:6789 -v change_me:/config -v change_me:/downloads –restart unless-stopped linuxserver/nzbget

In my other post, I covered SABnzbd but I’ve recently chosen to go with NZBGet on Docker as it has been more reliant in my lab. NZBGet’s default port is 6789 and if you don’t have a good reason, I would just keep it on the default port. NZBGet has one configuration less than Sonarr and Radarr:

/config
stores the configuration files

/downloads
download folder where your NZBGet is going to store all downloads. This folder needs to be accessible by Sonarr and Radarr.

Running Usenet Stack on Kubernetes

Some of the most common applications in a Usenet Stack are SABnzbd, Sonarr and Radarr. SABnzbd is a binary newsreader which handles download from Usenet. Sonarr acts a PVR for TV shows and Radarr is a fork of Sonarr is a PVR for Movies. This post will show to deploy a Usenet Stack on Kubernetes

I recently helped out a friend to get these apps deployed on Kubernetes and I published the YAML files. You can find the files on my Github repo but I will share them further down as well.

 

Read More

Kubernetes with Mixed CPU Architecture

Creating a Raspberry Pi Kubernetes cluster is straight forward, however it becomes more complicated when you want to mix and match kubernetes nodes of different CPU architectures.

I recently deployed a new Kubernetes cluster in my home lab which initially consisted of two Ubuntu nodes running kubeadm and are  VMs on VMware ESXi. Last night I tried to add a Raspberry Pi  and ran into a couple of issues which I resolved and describe further down to save you some time.

Read More