this post was submitted on 03 Feb 2026
88 points (93.1% liked)

Selfhosted

63216 readers
385 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] lambalicious@lemmy.sdf.org 13 points 8 months 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 8 months 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 8 months ago* (last edited 8 months 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.