Selfhosted

39452 readers

477 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

If you already know Docker CLI, is there a reason to use Portainer? (lemmy.zip)

submitted 4 hours ago by MoogleMaestro@lemmy.zip to c/selfhosted@lemmy.world

8 comments fedilink hide all child comments

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.

top 8 comments

sorted by: hot top controversial new old

[–] Pissio@feddit.it 3 points 1 hour ago

I’m using it to manage a little swarm , the useful thing is that is easy to explain to a non IT person how to log in and restart a service if needed.

[–] earth_walker@lemmy.world 8 points 3 hours ago

Like many GUIs it makes it so you don't have to remember and type a bunch of commands to carry out basic tasks. I especially find it convenient for checking logs. But no unique functionality compared to CLI. So it's a matter of preference.

[–] walden 10 points 4 hours ago

I switched from portainer to dockge. Dockge makes updating a 1-click process which I love. Portainer is overkill for homelab, but I like how it lists things like images and networks.

[–] grimer@lemmy.world 4 points 4 hours ago

95% of the time I'll use the CLI but occasionally it's faster for me to check a bunch of boxes in Portainer and restart entire stacks at the same time instead of going to each one's folder. Maybe a few other little things like that but you get the idea.

[–] catloaf@lemm.ee 3 points 4 hours ago (1 children)

It's a good way to have all the different parts exposed to you. Once you're familiar, it's usually easier to write those parts up in a compose file and just run or rerun docker-compose.

[–] yonder@sh.itjust.works 5 points 4 hours ago

This is exactly what I do. I find Portainer to be nice for getting an overview of my containers that are all created using docker-compose.

[–] just_another_person@lemmy.world 2 points 4 hours ago

It's just a front-end abstraction for different c ontainer backends, so no. I don't think they have some distinct features that deal in any functionality for the container ecosystem or anything.

[–] SeeJayEmm@lemmy.procrastinati.org 1 points 3 hours 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.