this post was submitted on 26 May 2026
25 points (93.1% liked)
technology
24374 readers
135 users here now
On the road to fully automated luxury gay space communism.
Spreading Linux propaganda since 2020
Rules:
- 1. Obviously abide by the sitewide code of conduct.
Bigotry will be met with an immediate ban
- 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
- 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
- 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
- 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
- 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
- 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.
founded 5 years ago
MODERATORS
Systemd lets me do my fun podman containers so this is cool by me
I'm a flatpak advocate and have been wanting better permission capabilities similar to Android, so I don't really care how they do it. I've never been presented with any reason as to why people dislike systemd other than "Linux is about choice", when the choices in my eyes are like having 50 cans of the same soup at the store with slightly different ingredients and half of them are expired.
Have you tried systemd-nspawn?
No but from like two Google searches it doesn't seem to be particularly suited to my use case. I'm just running a couple services like a music server and not a particularly advanced user
It's basically a more systemd-integrated version of docker/podman. I think you could run a container without too much trouble by creating an "OCI bundle" from an existing container image and running that. But you're right it might be slightly more hassle.