Docker container which runs SABnzbd while connected to OpenVPN.

This is an arm64 build of sabnzbdvpn container by Mumie-hub.

View on Docker Hub.

To run the container use this command for example:

docker run -d --name sabnzbdvpn \
            -v /host/storage/path:/config \
            -v /path/to/openvpnconfigdir:/etc/openvpn/custom
            -v /etc/localtime:/etc/localtime:ro \
            -e "LOCAL_NETWORK=192.168.0.0/24" \
            -p 8080:8080 \
            cheersmate/sabnzbdvpn

Docker compose:

name: <your project name>
services:
    sabnzbdvpn:
        container_name: sabnzbdvpn
        volumes:
            - /host/storage/path:/config
            - /path/to/openvpnconfigdir:/etc/openvpn/custom
            - /etc/localtime:/etc/localtime:ro
        environment:
            - LOCAL_NETWORK=192.168.0.0/24
        ports:
            - 8080:8080
        image: cheersmate/sabnzbdvpn

By default OpenVPN will run as the root user and SABnzbd will run as user abc 1003:1003. You may set the following parameters to customize the user id that runs SABnzbd.

If you set LOCAL_NETWORK correctly, the WebUI of SABnzbd should be at http://containerhost:8080. If its not responding, there might be an error with your LOCAL_NETWORK subnet settings.

The container supports the LOCAL_NETWORK environment variable. For instance if your local network uses the subnet 192.168.0.0/24 you should pass -e LOCAL_NETWORK=192.168.0.0/24. It must match your subnet, else your traffic will be "non-local" traffic and therefore be routed out through the VPN interface.

Alternatively you can reverse proxy the traffic through another container, as that container would be in the docker range. Nginx with proxypass config.

$ docker run -d \
      --link <sabnzbdvpn-containername> \
      --net <sabnzbdvpn-dockernetwork> \
      -v /path/to/customnginx.conf:/etc/nginx/nginx.conf:ro \
      -p 8080:8080 \
      nginx:latest

Add a new volume mount to your docker run command that mounts your config file:

-v /path/to/config.ovpn:/etc/openvpn/custom/default.ovpn

If you have an separate ca.crt file your volume mount should be a folder containing both the ca.crt and the .ovpn config.

If you are asked to enter your username and password when OpenVPN is initialising (due to auth-user-pass option being included in your config without an argument), add the following line to your .ovpn config file:

auth-user-pass /etc/openvpn/custom/pass.txt

Then create a bind mount to the file (containing your username and password separated by a line break) on your local machine. Eg. -v /path/to/pass.txt:/etc/openvpn/custom/pass.txt.

Some have encountered problems with DNS resolving inside the docker container. This causes trouble because OpenVPN will not be able to resolve the host to connect to. If you have this problem use dockers --dns flag to override the resolv.conf of the container. For example use googles dns servers by adding --dns 8.8.8.8 --dns 8.8.4.4 as parameters to the usual run command.

If the VPN connection fails or the container for any other reason loses connectivity, you want it to recover from it. One way of doing this is to set environment variable OPENVPN_OPTS=--inactive 3600 --ping 10 --ping-exit 60 and use the --restart=always flag when starting the container. This way OpenVPN will exit if ping fails over a period of time which will stop the container and then the Docker deamon will restart it.

When your are using a managed network layer for example, the default link mtu of 1500 can be to big. Setting a lower mtu in OpenVPN should help: -e OPENVPN_OPTS=--tun-mtu 1300

Run the container in privileged mode: --privileged or privileged: true for compose.