Exactly!

people act entitled as if all that you mention was trivial and that somehow FOSS devs “owe” people, but we only see those big corpos make it happen because… well, they’re big corpos, burning VC money on makint it happen and making it happen in a controlled jail.

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.

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.