I am actually using docker compose, I’ve tried their guide as well with no luck.

deleted by creator

Hmm, they’re not easily available in the EU it seems.

Also a US based company, if that matters to you.

I would consider that a downside TBH, but it’s hard to avoid unfortunately.

What would you recommend as a replacement with same level of novice-friendly UI/setup? I was looking to go down that route specifically because it seems like an easy way to get a solid network setup without being a network pro.

I’m running my smart home entirely from a single NUC running proxmox with VMs and LXCs for my services. It’s pulling ~7W on average

No they’re in the same compose file, I just left other parts out because it’s fairly long for a post.

Actually I’m also not using the default port for any of my qbit instances

IDK, it’s worth a try to rearrange the containers I would say.

Yeah i pretty much stole this from someone else, although it only used a single torrent client so i just added another that looked the same. i’m not very skilled in docker, so some things may not be best practice (or even correct)

qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrent
    network_mode: service:gluetun
    environment:
      - PUID=${APPUSER_PUID}
      - PGID=${APPUSER_PGID}
      - TZ=${TIME_ZONE_VALUE}
      - WEBUI_PORT=8084
    volumes:
      - ${PATH_TO_DATA}/qbit/config:/config
      - ${PATH_TO_COMPLETE}:/downloads
    restart: unless-stopped
    depends_on:
      - gluetun

  qbittorrentTL:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrentTL
    network_mode: service:gluetun
    environment:
      - PUID=${APPUSER_PUID}
      - PGID=${APPUSER_PGID}
      - TZ=${TIME_ZONE_VALUE}
      - WEBUI_PORT=8085
    volumes:
      - ${PATH_TO_DATA}/qbitTL/config:/config
      - ${PATH_TO_COMPLETE}:/downloads
    restart: unless-stopped
    depends_on:
      - gluetun

  gluetun:
    image: qmcgaw/gluetun
    container_name: gluetun
    networks:
      pirate_net:
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    environment:
      - VPN_SERVICE_PROVIDER=protonvpn
      - OPENVPN_USER=[USER]
      - OPENVPN_PASSWORD=[PASSWORD]
      - SERVER_COUNTRIES=[COUNTRIES]
      - VPN_PORT_FORWARDING=on
      - UPDATER_PERIOD=6h
    ports:
      - 8084:8084 # Qbit
      - 8085:8085 # QbitTL
      - 6881:6881
      - 6881:6881/udp
      - 8191:8191 # Flaresolverr
      - 9696:9696 # Prowlarr
      - 7878:7878 # Radarr
      - 8989:8989 # Sonarr
    volumes:
      - ${PATH_TO_DATA}/gluetun/config:/config

networks:
  pirate_net:
    driver: bridge

That’s really weird, I’m using the same image to run two instances of qbit behind gluetun without any issues whatsoever.

Funny, i couldn’t get HW encoding to work with the linuxserver.io docker image, but the exact same compose file, except it’s using the official image, works just fine without any issues.

I just bought a 4k 60hz loopthrough usb3 card so I can start saving the media I want from the services I still subscribe to. What software do you use for recording?

I didn’t say anything about variation between two screws of the same pitch

But this is what everyone else is talking about, because that’s what matters in this case. The manufacturer knows exactly what type of thread they used, and the variances within that type are really small, so they can easily tell how many mm of vertical movement 1/8 of a turn is with high consistency.

If you’re familiar with coffee grinders, they’re basically using thread to adjust distance between 2 burrs. Even there (mid to upper-mid range ones) can’t guarantee the same grind size on the same setting for different unit of the same model

While the coffee grinder example is true, this is not at all due to tolerances in the thread pitch used to adjust the distance.

This is because of the tolerances on the burrs themselves and the sideways alignment varies too much, and why it’s better on more expensive models.

Threads are controlled to a fairly tight ISO standard, which can be done very cheaply because of the simple helix shape and ridiculously large quantities.

Burrs on the other hand are much more complex shapes, in much lower quantities, which is why tight tolerances are expensive on coffee grinder burrs and not on simple thread pitches on standard bolts.

Getting a wire harness so I didn’t have to crimp all the wires myself is the main reason I ordered a kit instead of self-sourcing.