Live data from Hacker News

Transitioning from Docker to Podman

developers.redhat.com

11–20 of 278 posts

Re: Transitioning from Docker to Podman

#12
post #2

> One of Podman’s greatest advantages is its complete CLI compatibility with Docker. In fact, when building Podman, Docker users can adapt without any significant changes. For example, you can use the alias command to create a docker alias for Podman: `alias docker=podman` Wow that's a great adoption hack; just alias another program as another

Would that be covered by the same issue as Google v Oracle?

Re: Transitioning from Docker to Podman

#13
post #5

I really struggled with podman, a bunch of containers (I cant remember which ones) didn't work, and build tools choked as well. At work we dont get root access so I thought it would be perfect but sysadmins couldn't figure out how to configure either so was bust there too.

[deleted]

Re: Transitioning from Docker to Podman

#14
post #10
post #3

I like the daemonless architecture a lot, but until there's a quick and painless way to install it on OSX and Windows developer machines, you're going to see very limited uptake.

I was just thinking the same thing, and was going to ask if there was anything like Docker Desktop, something to make it simple to use on Windows/MacOS!

Before there was Docker Desktop on Mac there was Docker Machine.

And of course there's a Podman Machine: https://developers.redhat.com/blog/2020/02/12/podman-for-mac...

Re: Transitioning from Docker to Podman

#15
I was just about to complain about another thing to learn. Then I saw you can do "$ alias docker=podman". Just want to acknowledge the importance of that work. Making things compatible is both boring and a pain, but it's a door opener for people like me who refuse to learn your new API because I know a decent one already.

Re: Transitioning from Docker to Podman

#16
post #5

I really struggled with podman, a bunch of containers (I cant remember which ones) didn't work, and build tools choked as well. At work we dont get root access so I thought it would be perfect but sysadmins couldn't figure out how to configure either so was bust there too.

I've also personally struggled a lot with this at $WORK, but some of the new features in RHEL 7.8+ (specifically GA'ing of the fuse-overlayfs graph driver) have actually alleviated a ton of the issues I've seen previously. If you haven't tried that I'd certainly recommend it, YMMV

Re: Transitioning from Docker to Podman

#17
post #5

I really struggled with podman, a bunch of containers (I cant remember which ones) didn't work, and build tools choked as well. At work we dont get root access so I thought it would be perfect but sysadmins couldn't figure out how to configure either so was bust there too.

I had the opposite experiences, everything worked out of the box.

Re: Transitioning from Docker to Podman

#18
post #3

I like the daemonless architecture a lot, but until there's a quick and painless way to install it on OSX and Windows developer machines, you're going to see very limited uptake.

I actually like the idea of Docker as a better systemd (or rather, the interface is better). No bespoke file format, programmable API, no need to google for the right journalctl switches, and then of course the advantages of containers and images over processes and system packages. I’m not suggesting everything should be a container nor that docker is the ideal implementation, but it certainly points in the right direction.

Re: Transitioning from Docker to Podman

#19
post #5

I really struggled with podman, a bunch of containers (I cant remember which ones) didn't work, and build tools choked as well. At work we dont get root access so I thought it would be perfect but sysadmins couldn't figure out how to configure either so was bust there too.

I just installed my new $WORK docker-compose using podman and podman-compose, and it worked out of the box. To be fair, I failed at it one time before at previous job... So... Coin flip?

Re: Transitioning from Docker to Podman

#20

Any docker Podman corner cases that people have run into? I like the idea of rootless containers but I can do that ether easily by adding one line to my dockerfile or adding a user flag when I run a docker container. What other advantages am I getting?

No need to run a daemon. Security is better.
Post reply on HN