Selfhosted

39446 readers

486 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

[email protected]

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

submitted 2 hours ago by [email protected] to c/[email protected]

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

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 2 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 3 points 2 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.