Errors in Portainer when deploying Transmission stack

BKWayne · Jun 26th 2021

System info:

Raspberry Pi 4 (4GB)

Boot Disk - SanDisk 32GB UHS Class1

External - Toshiba 2TB USB 3.0 drive

Portainer Ver - 2.6.0

I was following Techno Dad Life's video "Easy Automated Home Media Server: VPN, Radarr, Sonarr, Lidarr, Librarian in 10 Minutes." And using the new docker-compose file from that video.

When I get to deploying the stack, Transmission is never created as container. All other services are in the "created" state for their containers but do not start since there is no Transmission container running. In addition, when going back to the stack, it shows "limited" and reports that the stack was not created in portainer, despite being pasted into the portainer web interface. I'm very much to OMV/Portainer so any and all help is appreaciated!

Here is the docker-compose file

Code

version: '2.1'
services:
 transmission-openvpn:
    volumes:
        - /srv/dev-disk-by-uuid-682875E32875B0A4/data/appdata/:/data
        - /etc/localtime:/etc/localtime:ro
    environment:
        - PUID=1000
        - PGID=1000
        - CREATE_TUN_DEVICE=true
        - OPENVPN_PROVIDER=SURFSHARK
        - OPENVPN_CONFIG=us-chi.prod.surfshark.com_udp
        # - NORDVPN_COUNTRY=US
        # - NORDVPN_CATEGORY=legacy_p2p
        # - NORDVPN_PROTOCOL=udp
        - OPENVPN_USERNAME=USERNAME
        - OPENVPN_PASSWORD=PASSWORD
        - OPENVPN_OPTS=--inactive 3600 --ping 10 --ping-exit 60
        - WEBPROXY_ENABLED=false
        - LOCAL_NETWORK=192.168.8.0/24
        - TRANSMISSION_SCRAPE_PAUSED_TORRENTS_ENABLED=false
        - DNS=8.8.8.8,8.8.4.4
    cap_add:
        - NET_ADMIN
    logging:
        driver: json-file
        options:
            max-size: 10m
    ports:
        - 9091:9091
        - 9117:9117
        - 7878:7878
        - 8989:8989
        - 8686:8686
        - 5299:5299
    restart: always
    image: haugene/transmission-openvpn:latest-armhf
 
 jackett:
    image: linuxserver/jackett
    container_name: jackett
    network_mode: "service:transmission-openvpn"
    environment:
        - PUID=1000
        - PGID=1000
        - TZ=America/New_York
        - AUTO_UPDATE=true #optional
        - RUN_OPTS=#optional
    volumes:
        - /srv/dev-disk-by-uuid-682875E32875B0A4/data/appdata/jackett:/config
        - /srv/dev-disk-by-uuid-682875E32875B0A4/data/downloads/watch:/downloads
        #Jackett only needs config
    restart: unless-stopped
 
 radarr:
    image: linuxserver/radarr
    network_mode: "service:transmission-openvpn"
    container_name: radarr
    environment:
        - PUID=1000
        - PGID=1000
        - TZ=America/New_York
        - UMASK_SET=022 #optional
    volumes:
        - /srv/dev-disk-by-uuid-682875E32875B0A4/data/appdata/radarr:/config
        - /srv/dev-disk-by-uuid-682875E32875B0A4/data/media/movies:/movies
    restart: unless-stopped
 
 sonarr:
    image: linuxserver/sonarr
    network_mode: "service:transmission-openvpn"
    container_name: sonarr
    environment:
        - PUID=1000
        - PGID=1000
        - TZ=America/New_York
        - UMASK_SET=022 #optional
    volumes:
        - /srv/dev-disk-by-uuid-682875E32875B0A4/data/appdata/sonarr:/config
        - /srv/dev-disk-by-uuid-682875E32875B0A4/data/media/tv:/tv
    restart: unless-stopped
 
 lidarr:
    image: linuxserver/lidarr
    network_mode: "service:transmission-openvpn"
    container_name: lidarr
    environment:
        - PUID=1000
        - PGID=1000
        - TZ=America/New_York
        - UMASK_SET=022 #optional
    volumes:
        - /srv/dev-disk-by-uuid-682875E32875B0A4/data/appdata/lidarr:/config
        - /srv/dev-disk-by-uuid-682875E32875B0A4/data/media/music:/music
    restart: unless-stopped
 
 lazylibrarian:
    image: linuxserver/lazylibrarian
    network_mode: "service:transmission-openvpn"
    container_name: lazylibrarian
    environment:
        - PUID=1000
        - PGID=1000
        - TZ=America/New_York
        # - DOCKER_MODS=linuxserver/calibre-web:calibre #optional
    volumes:
        - /srv/dev-disk-by-uuid-682875E32875B0A4/data/appdata/lazylibrarian:/config
        - /srv/dev-disk-by-uuid-682875E32875B0A4/data/media/:/media
    restart: unless-stopped

Display More

chrisblack · Jun 27th 2021

Watching as I have the same or similar issues

KM0201 · Jun 27th 2021

This is going to be long as I'll try to be detailed, but a few things popped out to me. While I can't say these are your problems, and understanding I've never watched the video for more than a couple minutes...

1. All of your "linuxserver" image names have been deprecated for some time... I think they *should* still pull the proper image, but you might as well start using the proper image names as a first trouble shooting step... Eventually I'm sure those names will stop working

Example... Look at the docker-compose and look at the image name for lazylibrarian. All of the linuxserver images changed similarly:

https://hub.docker.com/r/linuxserver/lazylibrarian

2. Your network modes don't look right. Maybe it works, but I've routed many containers through my "swag" container, and it just didn't look like that. First, since these are all being deployed (presumably) in the same stack, you shouldn't even need network mode... as they will all go through the first containers network (in this case, transmission-vpn).. even if you needed network mode however.. it still doesn't look right.

Here's what I would do...

1. Delete the entire stack and all associated images and containers.

2. Click on Networks in Portainer, and delete all unused networks

3. Create a new stack, this time, just run and setup transmission-vpn. Once transmission is set up and working... You can do one of two things to add another service to it:

4. Add another service (ie, jackett) to the transmission stack. In this case, completely delete that network mode line. Redeploy the stack... see if jacket is working. Because it is getting deployed in the same stack as transmission, it should automatically get assigned to the same network. Make sure you're using the proper image name from the services linuxserver dockerhub page.

hope that helps

BKWayne · Jun 27th 2021

Thanks! That's all very helpful. Appreciate your time.

Portainer gave me an error for the transmission image not being found. I went to the site and checked, and deleted the "latest-armhf" and then the stack deployed.

The container reports back "unhealthy". I've attached the log file and included everything before the first restart where it all seems to be repeating after.

_vpn_transmission-openvpn_1_logs (1).txt

chrisblack · Jun 27th 2021

I removed the :latest-armhf" and tried it again this afternoon and got it to install this time as well. Mine seems to be in a loop: Fatal Python error: pyinit_main: cant initialize time

permissionError: operation not permitted

options error: you must define tun/tap device)--dev)

(I did uninstall portioner and docker and reinstall both yesterday when trying.)

Morlan · Jun 28th 2021

https://docs.linuxserver.io/faq

BKWayne · Jun 28th 2021

That did the trick! Followed the guide for option 2 and now have a "healthy" status.

One last (potentially stupid) question, since I will be trying to deploy the rest of the containers in the stack without a network mode, how can I verify that are running through the VPN?

gderf · Jun 29th 2021

Quote from BKWayne

One last (potentially stupid) question, since I will be trying to deploy the rest of the containers in the stack without a network mode, how can I verify that are running through the VPN?

All depends on the application and if it was built with internal tools such as curl. So try this and see.

Get a shell inside a container: docker exec -it <container-name> /bin/bash

You can also get a shell inside a container via Portainer using the Quick Actions Exec Console in the Container list.

Run this command at the shell prompt and examine the returned IP address: curl ifconfig.io

If the returned IP is your public IP, then you are not connecting thru the VPN. FIND OUT WHY.

For any torrent application you should always be running a tracker IP ID torrent. This will show you what the trackers see as your IP address. Make sure it isn't your public IP address. Go here and follow directions:

https://trak.evilvibes.com/

chrisblack · Jul 10th 2021

Quote from BKWayne

I was confused by where I should run the script. I was expecting I had to run them on OMV and not just the Raspberry pi. I ssh into the pi and ran them there as a test and it worked for me as well. Thank you all! Now to see if they actually run and work properly.

Errors in Portainer when deploying Transmission stack

Participate now!

Tags