Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Podman v6.0.0

blog.podman.io

Post reply on HN
Print view View original

91–100 of 269 posts

Re: Podman v6.0.0

#91

Post by hadlock »

Chyzwar wrote: post #44
SwellJoe wrote: post #4

No idea why Docker is still so much more popular than Podman. Podman is obviously the better implementation. The new network stuff is a welcome improvement.

Last time I evaluated podman, Ubuntu was second class citizen. Rootless was non trivial and required additional setup. Documentation also suck. Docker is something we all already hate, milion edge cases and forever bugs but at least well documented and understood. Podman claim to be drop-in replacement does it mean it carry docker shitness? Examples: ufw punch through, env file handling, volumes, etc

One of the key design principles of podman was rootless operation; they were so disgusted by Docker being a daemon they decided to do a full open source implementation. I've never had an issue with it running without root.

Re: Podman v6.0.0

#92

Post by tormeh »

sudonem wrote: post #73
SwellJoe wrote: post #4

No idea why Docker is still so much more popular than Podman. Podman is obviously the better implementation. The new network stuff is a welcome improvement.

I’d wager it’s mainly just that deployment is mildly more annoying and requires more disparate steps. Especially if you want to go rootless (and you should). For someone that isn’t “Linux first” (like a baby developer learning to containerize their apps), the idea of dealing with systemd unit files or kublet configs, and having to created dedicated local service accounts (and remembering to enable linger) is somewhat…

Are we talking windows here? On Linux and Mac I believe you can install Podman via a package manager like anything else.

Re: Podman v6.0.0

#94

Post by noxvilleza »

raffraffraff wrote: post #79
Chyzwar wrote: post #44

Earlier quoted context omitted.

Last time I evaluated podman, Ubuntu was second class citizen. Rootless was non trivial and required additional setup. Documentation also suck. Docker is something we all already hate, milion edge cases and forever bugs but at least well documented and understood. Podman claim to be drop-in replacement does it mean it carry docker shitness? Examples: ufw punch through, env file handling, volumes, etc

Last time I tried rootless podman was about 6 months ago and it was a total mess. I was trying to use it to run a container as me (user 1000) and mount a directory from my home (owned by user 1000) and it drove me and Claude around the bend. It's not a podman vs docker thing per se, just rootless being a total pain. However I just enabled the docker service, ran the same command on docker and it worked. I think I jus…

Had similar issues with podman on a Steam Deck of mine that I use as a little home server - eventually got a configuration working fine but was a real pain.

Re: Podman v6.0.0

#95

Post by zdragnar »

sph wrote: post #55
zdragnar wrote: post #5

Earlier quoted context omitted.

You've come to the wrong website to complain about contrast issues, my friend.

? HN’s contrast is great. It’s black on a light yellow-beige.

SO much of the text of a comment thread is not black, though. The line above each comment is gray. Downvoted comments are various shades of gray. The "help" link next to the comment box is gray.

I've seen worse, but gray on beige is not my favorite.

Re: Podman v6.0.0

#96

Post by sudonem »

tormeh wrote: post #92
sudonem wrote: post #73

Earlier quoted context omitted.

I’d wager it’s mainly just that deployment is mildly more annoying and requires more disparate steps. Especially if you want to go rootless (and you should). For someone that isn’t “Linux first” (like a baby developer learning to containerize their apps), the idea of dealing with systemd unit files or kublet configs, and having to created dedicated local service accounts (and remembering to enable linger) is somewhat…

Are we talking windows here? On Linux and Mac I believe you can install Podman via a package manager like anything else.

Linux. It’s not the installation of podman that can be fiddly. It’s the setting up systemd unit files and local user accounts for rootless / daemonless deployment of containerized apps that can be a headache.

It’s not hard. It’s just fiddly.

Re: Podman v6.0.0

#98

Post by buredoranna »

Top of my list as to why I prefer podman...

no "container root" / "docker group" = "host root" shenanigans

podman doesn't spew garbage and punch holes in my firewall (iptables)

(edit: formatting)

Re: Podman v6.0.0

#99

Post by drnick1 »

sudonem wrote: post #73
SwellJoe wrote: post #4

No idea why Docker is still so much more popular than Podman. Podman is obviously the better implementation. The new network stuff is a welcome improvement.

I’d wager it’s mainly just that deployment is mildly more annoying and requires more disparate steps. Especially if you want to go rootless (and you should). For someone that isn’t “Linux first” (like a baby developer learning to containerize their apps), the idea of dealing with systemd unit files or kublet configs, and having to created dedicated local service accounts (and remembering to enable linger) is somewhat…

> the idea of dealing with systemd unit files or kublet configs, and having to created dedicated local service accounts

Podman does not require systemd (thank God). I use a simple podman compose up/down in a user systemd file to automatically bring my containers up at boot, but other mechanisms are possible, like quadlets and init scripts.

Re: Podman v6.0.0

#100

Post by drnick1 »

sudonem wrote: post #96
tormeh wrote: post #92

Earlier quoted context omitted.

Are we talking windows here? On Linux and Mac I believe you can install Podman via a package manager like anything else.

Linux. It’s not the installation of podman that can be fiddly. It’s the setting up systemd unit files and local user accounts for rootless / daemonless deployment of containerized apps that can be a headache. It’s not hard. It’s just fiddly.

> It’s just fiddly.

You could quite simply have a systemd file that calls podman compose up when the service starts and podman compose down when it stops. Basically the same systemd file for every container stack defined in a single compose.yml. It's extremely easy, and does not do stuff behind your back like Docker (such as silently altering iptables rules).

Post reply on HN