SeeJayEmm

@SeeJayEmm@lemmy.procrastinati.org

• ⁨Comment⁩ on ⁨If you already know Docker CLI, is there a reason to use Portainer?⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  Only by exposing the docker socket. And it doesn’t support managing network or volumes.

• ⁨Comment⁩ on ⁨If you already know Docker CLI, is there a reason to use Portainer?⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  The constant argument in this space that you must know the arcane workings of everything you use, is exhausting.

• ⁨Comment⁩ on ⁨If you already know Docker CLI, is there a reason to use Portainer?⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  Just 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.

• ⁨Comment⁩ on ⁨If you already know Docker CLI, is there a reason to use Portainer?⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  Personal preference? I prefer the Portainer’s presentation over the CLI. I especially find it easier to manage networks and volumes.

  But my main reason is I have multiple docker hosts and it gives me a “single pane on glass” to manage everything from.