Comment

Comment on If you already know Docker CLI, is there a reason to use Portainer?

gamermanh@lemmy.dbzer0.com ⁨17⁩ ⁨hours⁩ ago

What works for me:

Networks first in docker-compose

Gluetun first in Services, uses the network I set for it and the stack

Everything else goes below it, relying on the gluetun CONTAINER (I plan to have another stack running gluetun for other reasons so having it check the service is a no go for me) to be running in a HEALTHY state

All are set to restart: unless-stopped except gluetun, which is never

The expected behaviour is that containers will always wait for gluetun to report that it’s healthy before trying again to restart. Should gluetun fail and crash for any reason it won’t reboot and potentially fuck itself up harder, and no services will be able to start because it’s not reporting healthy.

This works perfectly in portainer and should when running docker-compose up, but for me it took portainer to work. Saw someone somewhere mention it has some sort of priority handling override built into it that docker itself doesn’t, meaning it’s less likely to fuck that lind of thing up, but idk how true it is

I’ll see if I can remember to snag a couple snips of my YAML to make it more clear

source

Sort:hotnew top

aStonedSanta@lemm.ee ⁨17⁩ ⁨hours⁩ ago

Awesome. Thank you so much. Saving this for when I get back into town. Gonna fuck around and find out Monday 💜🙏

source

gamermanh@lemmy.dbzer0.com ⁨16⁩ ⁨hours⁩ ago

Ok, had my wife send me the file from my network

networks:

  main-network:

    name: ${COMPOSE\_PROJECT\_NAME}

    attachable: true

    ipam:

      driver: default

      config:

        - subnet: configure

          ip\_range: this

          gateway: yoself

services:

\# Gluetun - <https://github.com/qdm12/gluetun>

  gluetun:

    image: qmcgaw/gluetun

    container\_name: gluetun

    networks:

      - main-network

    cap\_add:

      - NET\_ADMIN

    environment:

      - PUID=${PUID}

      - PGID=${PGID}

      - TZ=${TZ}

      - VPN\_SERVICE\_PROVIDER=custom

      - VPN\_TYPE=wireguard

      - VPN\_PORT\_FORWARDING=true

      - VPN\_PORT\_FORWARDING\_PROVIDER=protonvpn

      - WIREGUARD\_ADDRESSES=use your own

      - WIREGUARD\_ALLOWED\_IPS=0.0.0.0/0

      - WIREGUARD\_PRIVATE\_KEY=nope

      - WIREGUARD\_PUBLIC\_KEY=69420

      - WIREGUARD\_DNS=

      - VPN\_ENDPOINT\_PORT=

      - VPN\_ENDPOINT\_IP=

    volumes:

      - ${DOAPPDAT}/gluetun:/gluetun

I left in the wireguard stuff without my details because for me Gluetun refused to work when setting the exact same info to wg0.conf, so I define it in my compose

Then, services that rely on gluetun go below and look like:

\# qBittorrent - <https://hub.docker.com/r/linuxserver/qbittorrent>

  qbittorrent:

    container\_name: qbittorrent

    network\_mode: container:gluetun

    image: [lscr.io/linuxserver/qbittorrent:latest](http://lscr.io/linuxserver/qbittorrent:latest)

    depends\_on:

          gluetun:

              condition: service\_healthy

    restart: unless-stopped

Works perfectly when I run it through portainer

source

one_knight_scripting@lemmy.world ⁨12⁩ ⁨hours⁩ ago
Wow. What an awesome wife. I think I just discovered a new relationship goal.

source
aStonedSanta@lemm.ee ⁨15⁩ ⁨hours⁩ ago
Thank you so much. 😊 I see a few things already worth changing in my file. You da best.

source
- gamermanh@lemmy.dbzer0.com ⁨14⁩ ⁨hours⁩ ago
  It took me too long to get everything working myself because people love to share shit exclusively in CLI format and look down at anyone who asks for YAML it seems, so I’m always glad to pass it on
  
  (I can understand CLI, but the ADHD brain finds YAML much easier for documentation purposes and it surprises me how many people seem to disagree)
  
  source
  - -> View More Comments