services:
  qbittorrent_open:
    container_name: qbittorrent_open
    image: ghcr.io/hotio/qbittorrent:release-5.1.2
    ports:
      - "8080:8080"
      - "42078:42078"
    restart: always
    environment:
      - PUID=1000
      - PGID=1000
      - UMASK=022
      - TZ=America/New_York
    mem_limit: 4g
    memswap_limit: 4g
    volumes:
      - /srv/qbittorrent_open-config:/config
      - nas_media:/data
      - /mnt/nas_library:/library
  qbittorrent_vpn:
    container_name: qbittorrent_vpn
    image: ghcr.io/hotio/qbittorrent:release-5.1.2
    ports:
      - "8088:8088"
    restart: always
    environment:
      - PUID=1000
      - PGID=1000
      - UMASK=022
      - TZ=America/New_York
      - WEBUI_PORTS=8088/tcp,8088/udp
    mem_limit: 3g
    memswap_limit: 3g
    volumes:
      - /srv/qbittorrent_vpn-config:/config
      - nas_media:/data
  qbittorrent_eXoDOS:
    container_name: qbittorrent_eXoDOS
    image: ghcr.io/hotio/qbittorrent:release-5.1.2
    ports:
      - "8089:8089"
    restart: always
    environment:
      - PUID=1000
      - PGID=1000
      - UMASK=022
      - TZ=America/New_York
      - WEBUI_PORTS=8089/tcp,8089/udp
    mem_limit: 3g
    memswap_limit: 3g
    volumes:
      - /srv/qbittorrent_eXoDOS-config:/config
      - nas_media:/data

volumes:
  # External volume; actual definition lives in `docker volume create` (see
  # NAS-CONNECTION-STRATEGIES.md). Current opts (fixed 2026-09-16 after a
  # host reboot broke this): type=nfs, vers=3 (not 4 - Docker's local volume
  # driver calls mount(2) directly rather than through the mount.nfs
  # userspace helper, which fails with "protocol not supported" for
  # nfsvers=4 on current nfs-utils/kernel), device=192.168.1.192:/mnt/user/media
  # (host must be in the device string itself now, not split into a
  # separate addr= option - nfs-utils 2.6.4 on Ubuntu 24.04 no longer
  # accepts the old ":/path" + addr= form).
  nas_media:
    external: true

networks:
  default:
    external:
      name: npm-network