Selfhosted @lemmy.world MoogleMaestro @lemmy.zip 1mo ago

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

I often see people mention the Portainer project and how it's useful, but I never hear any reason to use it other than as a more user friendly front end to service management.

So is there any particular feature or reason to use portainer over docker's CLI? Or is it simply a method of convenience?

This isn't only strictly for self hosting, but I figure people here would know better.

You're viewing a single thread.

41 comments

My main 2 reasons for installing it both come from needing to restart services sometimes:

Portainer let me allow other people access to restarting specific containers that occasionally misbehave

Portainer lets me update and restart all of the containers running in my VPN stack without breaking. For some ungodly reason, even with dependency set and everything in docker-compose, a CLI reboot will basically always start a service or 2 before gluetun is actually advertising it's in a healthy state and everything breaks. With portainer that doesn't happen, with the exact same compose, and I don't get why lol
- And then there is me. I had to start my stack 7 times yesterday in portainer. I should really figure out how to set it up right. I had thought setting gluetun to a static IP would get it to launch first. Or adding it to the top of the config. But alas. No go.
  
  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
  
  Awesome. Thank you so much. Saving this for when I get back into town. Gonna fuck around and find out Monday 💜🙏
  
  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 depends_on: gluetun: condition: service_healthy restart: unless-stopped
  
  Works perfectly when I run it through portainer
  
  Wow. What an awesome wife. I think I just discovered a new relationship goal.
  
  It worked. Muahaha it worked. Thank you so much. I still have so much to learn. But one click and repulled and redeployed. The only change I needed in my config was to add.
  
  depends_on: gluetun: condition: service_healthy
  
  Into each container that was controlled by gluetun
  
  Thank you so much. 😊 I see a few things already worth changing in my file. You da best.
  
  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)
  
  Haha dude. ADHD brain over here agrees. I can use CLI also but prefer not too

41 comments