Comment on If you already know Docker CLI, is there a reason to use Portainer?
SeeJayEmm@lemmy.procrastinati.org 22 hours agoJust because something doesn’t fit your use case doesn’t make it a terrible product. Portainer isn’t meant to complement managing docker via CLI. It’s meant to be the management interface.
If you want to manage your environment via CLI, I agree, don’t use Portainer. If you’re content (or prefer) a GUI, Portainer is a solid option. Esp if you have multiple hosts or want to manage more than just the compose stack. Last time I checked Dockge doesn’t do either.
ShortN0te@lemmy.ml 21 hours ago
The thing is, those poor design decisions have nothing to do with those features, i claim that every feature could be implemented without “holding the compose files hostage”.
Btw. dockge does support connecting to another docker dockge instance.
Voroxpete@sh.itjust.works 19 hours ago
Yes, this is exactly my point. I think I’ve laid out very clearly how Portainer’s shortcomings are far more than just “It’s not for your use case.”
Portainer is designed, from the ground up to trap you in an ecosystem. The choices they made aren’t because it’s necessary to do those things that way in order to be a usable Docker GUI. It’s solely because they do not want you to be able to easily move away from their platform once you’re on it.
SeeJayEmm@lemmy.procrastinati.org 21 hours ago
Only by exposing the docker socket. And it doesn’t support managing network or volumes.