this post was submitted on 03 Feb 2026
79 points (93.4% liked)

Selfhosted

56642 readers
414 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

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

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
top 9 comments
sorted by: hot top controversial new old
[–] _Nico198X_@europe.pub 15 points 2 weeks ago

LOVE podman

[–] lambalicious@lemmy.sdf.org 12 points 2 weeks ago (1 children)

It's pretty great, and I like that the workflow for creating containers is sliiiightly easier than on Docker. I switched from Docker to Podman for most stuff about a year ago and so far there are only two hiccups that I lament:

  • the higher disk consumption due to not being able to share image storage. (I've tried with additionalstorages but that seems to only be respected for podman run; podman build and podman compose seem to ignore it and always pull images from the registries)

  • Some annoying isses with fule permissions due to rootless design - running rootless containers will create files under your user storage that you as a user have no permission to transfer or remove for cleanup or security, and severely breaks the output of tools like du or find due to error spammage.

[–] Jayjader@jlai.lu 6 points 2 weeks ago (1 children)

In case you omitted the following out of ignorance and not by deliberate choice:

podman unshare can be used to (mostly) painlessly access the files created by rootless podman.

[–] lambalicious@lemmy.sdf.org 4 points 2 weeks ago* (last edited 2 weeks ago)

Oh thanks, I know well about it. podman unshare is the reason why those permission issues are not major (eg.: you don't need to ever sudo to solve the permission issues rootless causes, I think?). But my going to was more focused o borking the output or workflow of using some of the "usual" tools of a Linux console, such as needing to account for the potential existence of a podman environment on the user account (or any given user account, if doing house cleaning under root) if you ever need to rely on the recursive results of things like chmod or find.

[–] tau@infosec.pub 11 points 2 weeks ago

Always great to see more Podman, especially rootless!

[–] flango@lemmy.eco.br 4 points 2 weeks ago (1 children)
[–] sv1sjp@lemmy.world 3 points 2 weeks ago

Thank you🚀🚀

[–] trolololol@lemmy.world 4 points 2 weeks ago (1 children)

I've heard of podman quite a bit but never tried it.

Is it truly free and open source?

Does it run only in Linux?

[–] chicuongle@lemmy.world 5 points 2 weeks ago

I think that is a question about trust and time. As long as Redhat does not change their policy, YES. For an open source project is it very important if the community is big enough to defense big tech desire for money. In my opinion, Red Hat hat a very good business model to balance and in long time Podman will be free