Selfhosted

44902 readers

616 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:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

[email protected]

Advantages of rootless podman? (sh.itjust.works)

submitted 1 week ago* (last edited 1 week ago) by [email protected] to c/[email protected]

27 comments fedilink hide all child comments

From what I have seen, rootless podman seems to take more effort (even if marginal) than rootful one. I want to make a more informed decision for the containers, so I would like to ask.

What is a rootless podman good for? How much does it help in terms of security, and does it have other benefits?
One of the benefits commonly mentioned is for when container is breached. Then, running container on sudo-capable user would give no security benefits. Does it mean I should run podman services on a non-privileged user?

Thank you!

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

[–] [email protected] 1 points 1 week ago (1 children)

            
              What is the benefit of creating users for every service? Wouldn't one be sufficient?
Also just out of curiosity, why not in sodo'ers list?

[–] [email protected] 9 points 1 week ago* (last edited 1 week ago)

Maybe one would be sufficient, but for better separation and to have a single startup script for every service I prefer to keep them on different users.

In this way, also the data of each service is created with a different user and cannot be messed up by a rogue service...

And why let that user access root in any way? Even via sudo? No need. No risk.

One service one user. Simple security and separation policy