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

Docker is dead? Podman – an alternative tool?

content.fme.de

Post reply on HN
Print view View original

31–40 of 183 posts

Re: Docker is dead? Podman – an alternative tool?

#31

Post by mati365 »

colordrops wrote: post #18

NixOS recently switched the default from docker to podman for containers. I don't know if it's Nix's configuration, or a problem with Podman itself, but it's unusable. The systemd service often hangs, creating networks errors out, the pod concept doesn't work great, requiring tearing down the whole group of containers to change port mappings, and it acts like a completely different system depending on the user runnin…

It's also happening on Debian. Podman seems to be also losing quite often network firewall configuration after killing containers that were using cached images so you are not able to access internet from containers (logs say its libpodman bug)

Re: Docker is dead? Podman – an alternative tool?

#33

Post by pkulak »

qbasic_forever wrote: post #29

Rootless podman is my first choice for using containers now, it works fantastically well in my experience. It's so much nicer to have all my container related stuff like volumes, configs, the control socket, etc. in my home directory and standard user paths vs. scattered all over the system. Permission issues with bind mounts just totally disappear when you go rootless. It's so much easier and better than the root pr…

The arch wiki is my go to every time I install Podman, and it’s a little easier every time. It’s down to like two steps now, with no file editing. We’ll get there.

Re: Docker is dead? Podman – an alternative tool?

#34

Post by bob778 »

colordrops wrote: post #18

NixOS recently switched the default from docker to podman for containers. I don't know if it's Nix's configuration, or a problem with Podman itself, but it's unusable. The systemd service often hangs, creating networks errors out, the pod concept doesn't work great, requiring tearing down the whole group of containers to change port mappings, and it acts like a completely different system depending on the user runnin…

Podman always feel like software no one’s using in prod. There’s a lot of edge cases and bugs - particularly in the service control, user groups and ipv6 support

Re: Docker is dead? Podman – an alternative tool?

#35

Post by bob778 »

encryptluks2 wrote: post #28
throwawei369 wrote: post #16

This would all be true if podman wasn't a gimped version of docker.

In my experience it is quite the opposite really, a more featureful solution with much more options and safer defaults.

From using podman in prod, it seems to be lots of features but not necessarily stable or well-rounded

Re: Docker is dead? Podman – an alternative tool?

#36

Post by pkulak »

jcastro wrote: post #20
jordemort wrote: post #11

Why not both? Since Podman 4.1 came out with full Compose 2.x compatibility, I'm running Podman on Docker's socket, but using Docker's CLI to talk to it, so that I can use the buildx and compose CLI plugins. It works great, Docker's CLI doesn't seem to have any clue that it's talking to not-Docker. I even have VSCode's Docker extension and Remote Containers working this way.

Is there any config to set up this way or do you literally just run podman on the socket and it just knows what to do?

You can set it as systemd socket service, so it doesn’t even run until something tries to connect.

That said, I don’t even bother with that. Podman can run K8s configs, and they are yaml too, only slightly more verbose than a compose file, if you strip everything out you don’t need. The CLI is nicer than compose too, with proper commands instead of tying up a terminal until a ctrl-c.

Re: Docker is dead? Podman – an alternative tool?

#37

Post by usr1106 »

This article is from a Windows perspective.

On Linux podman is significantly different from docker: It uses user namespaces. So it is much more secure (assuming that security bugs related to Linux user namespaces, which have indeed been dicovered, are still much rarer than people running untrusted container images). However, with security comes incompatibility. If the image does tricky system interaction instead of just running user space code and some standard cases like opening a socket chances are that things will not work under podman without modification.

Re: Docker is dead? Podman – an alternative tool?

#39

Post by jdoss »

I only use Podman for my workloads these days. Docker was always a headache for me on Linux. Podman allows me to quickly do whatever I want with containers and I can use systemd or a simple bash script to easily create services on my workstation or in production with Nomad with https://github.com/hashicorp/nomad-driver-podman

I am super thankful for the team of developers that work on Podman. It has really come a long way since 2.0 and they are very responsive to issues in my experiences. If you are using Linux as your daily driver and you use Containers give Podman a try. Here are some examples of the things I have done with Podman.

https://github.com/forem/selfhost

https://github.com/jdoss/ppngx

https://gist.github.com/jdoss/25f9dac0a616e524f8794a89b7989e...

https://gist.github.com/jdoss/ad87375b776178e9031685b71dbe37...

Re: Docker is dead? Podman – an alternative tool?

#40

Post by iknownothow »

It's okay to stick with Docker if it works for us right? There's nothing fundamentally wrong with it right?

At the moment Podman is just more work for us because I and other devs don't have years of of experience and intuitions about Podman like we have with Docker. I'd rather just focus on business problems rather than another migration.

Post reply on HN