Comment by dbacar
2 months ago
This is one of the main reasons people like Podman. Docker has this "feature" but as far as I remember, it needed some obscure configuration. I guess they don't add it as default as it will break many current setups.
2 months ago
This is one of the main reasons people like Podman. Docker has this "feature" but as far as I remember, it needed some obscure configuration. I guess they don't add it as default as it will break many current setups.
Please stop spreading this toxic curl|sh nonsense. It's wildly corrosive to security and system stability.
Is it really that much worse than using a package manager that drops a binary that you're not going to inspect anyways?
7 replies →
this is a thread about agents that run random things on your computer as root because they feel like it. curl|sh somehow seems mild in comparison
Whilst true, you can pretty easily assume and validate the result of that command.
That and podman lets you configure away from docker.io.
Podman has lots of underappreciated features, and it's fully open-source!
hmmm, care to tell us a few of them?
I would also add buildah and skopeo to the mix of things that podman does better. also, podman desktop has better licensing that docker desktop. podman is modular and as such they could easily change the way they do networking over time, for once it doesn't break iptables and firewall rules by design but rather works together with the security design around these tools.
Kube play and quadlets are cool
Apart from rootless, main winning point is daemonless running of the containers. There is no podman service.
Running systemd inside a container + automatic SELinux integration