2026-07-23 16:24 UTC
Moved off of portainer and onto dockge today. I was so SICK of never knowing where a docker compose's . volumes would end up and having to manually rework everything.
Was pretty easy to sort out and I'm glad I'll never run into a 500 error with no debug information at all and a half up mess of orphans splattered all over the walls.
Good stuff!
https://dockge.kuma.pet/
#homelab #docker
Replies (1)
-
@homelabista@mastodon.social 2026-07-23 19:02
The thing that finally made it click for me: compose namespaces named volumes by project name, and that defaults to the folder the compose file sits in. So the same db_data in two stacks ends up as stackA_db_data and stackB_db_data under /var/lib/docker/volumes. Lose track of one and `docker volume inspect ` prints the real Mountpoint. Dockge just makes that layout predictable from the start.