Live data from Hacker News

How to Replace Docker with Podman on a Mac

redhat.com

31–40 of 90 posts

Re: How to Replace Docker with Podman on a Mac

#31
post #13

Earlier quoted context omitted.

I like Multipass a ton, but as with almost every Docker/VM/Linux config right now, support on the M1 Mac is mixed. (Yes, yes, I know Docker Desktop works on the M1 now. But not all container images do, some run emulated, some break, there are still lots of papercuts.) I’ve had some success with the most recent builds of Multipass, but it isn’t reliable. For devs who still have access to an Intel Mac, I personally wou…

That might be a fun project if Hacktoberfest comes back this year, get open source projects building images for arm64. A lot of times it’s easy to do.

That’s actually a great idea!!

Re: How to Replace Docker with Podman on a Mac

#34

My understanding is that this old article is no longer the simplest/easiest way of doing this. For that, see https://marcusnoble.co.uk/2021-09-01-migrating-from-docker-t... . tl;dr: $ brew install podman $ podman machine init $ podman machine start $ alias docker=podman If you're on an M1 you may run into https://github.com/containers/podman/issues/10577 (which is WIP, and may have been resolved by https://github.com…

Does this work with compose? Probably not but just wondering

The problem with making this work, IIRC, is that Docker Compose doesn't actually "compose" Docker commands, but instead _re-implements_ a bunch of functionality itself through its Python libraries. So you'd actually need to bring your own CLI-compatible Docker Compose implementation for Podman rather than just making your Docker replacement compatible.

Re: How to Replace Docker with Podman on a Mac

#35
post #30
post #26

Earlier quoted context omitted.

As a typical mac user there is no practical benefit. Being on a Mac is so you can avoid lengthy configurations, scripts and commands and instead have something that just works and is seamlessly integrated. This is the opposite. You’d probably only want to go this route to make a statement about free open source software. But at that point you may as well run Linux

The Docker daemon (likely the HyperKit VM) on the Mac has a tendency to burn CPU cycles, even when there are no containers running. It's pretty common for it to sit at 10-20% of a core all day, and sometimes gets pegged at 100% until you quit. There are countless closed issues in the GitHub issue tracker [1] for similar issues, but the symptoms don't seem to go away for me or many of my colleagues. It's been a pretty…

I had the same frustrations until the other day I saw a tip to enable 'Use the new Virtualization framework' under Preferences -> Experimental Features. Since then Docker's background CPU usage has dropped to 1% and I no longer bother stopping it when I'm not using it.

Re: How to Replace Docker with Podman on a Mac

#36
This feels like the whole industry is now all going through the same motions…

I tried podman; two hurdles I haven't figured out: 1/ sending the context is incredibly slow on podman, compared to Docker+Buildkit. It's definitely trying to send literally the entire context, like Docker without Buildkit does, but even more slowly… 2/ private registry auth. Haven't really tried too hard, but it's not just "a drop in replacement"; I think I need to somehow auth with podman specifically. (Part of this is our external registry is ACR, and we auth with `az`, but I think `az` is presuming Docker…)

Re: How to Replace Docker with Podman on a Mac

#37
post #30

Earlier quoted context omitted.

The Docker daemon (likely the HyperKit VM) on the Mac has a tendency to burn CPU cycles, even when there are no containers running. It's pretty common for it to sit at 10-20% of a core all day, and sometimes gets pegged at 100% until you quit. There are countless closed issues in the GitHub issue tracker [1] for similar issues, but the symptoms don't seem to go away for me or many of my colleagues. It's been a pretty…

I had the same frustrations until the other day I saw a tip to enable 'Use the new Virtualization framework' under Preferences -> Experimental Features. Since then Docker's background CPU usage has dropped to 1% and I no longer bother stopping it when I'm not using it.

Wow, Mac users put up with some bullshit to avoid configuration and have things "just [sometimes, unless you're holding it wrong] work"

Re: How to Replace Docker with Podman on a Mac

#38

My understanding is that this old article is no longer the simplest/easiest way of doing this. For that, see https://marcusnoble.co.uk/2021-09-01-migrating-from-docker-t... . tl;dr: $ brew install podman $ podman machine init $ podman machine start $ alias docker=podman If you're on an M1 you may run into https://github.com/containers/podman/issues/10577 (which is WIP, and may have been resolved by https://github.com…

Does this actually work for you? I tried it and networking was broken out of the box – it couldn’t even pull a container image. I didn’t have time to spend digging into it, however, and would not rule out that being an artifact of our VPN.

Re: How to Replace Docker with Podman on a Mac

#39
post #19

I tried podman on an intel mac and everything worked except mounting volumes

Volumes are one of those things that Just Don't Work, even in normal Docker. Our product's dev containers run fine in Docker on macOS on M1 but the filesystem permissions get messed up when running the same ones on Linux. It's just a silly root:root permissions issue, but it's irritating the problem was hidden when running on a Mac.

There is some support for id mapping in the 5.12 kernel that we may be able to take advantage of for this case. Will have to take a look at how to deal with this for things like volumes.

https://man7.org/linux/man-pages/man2/mount_setattr.2.html#N...

Re: How to Replace Docker with Podman on a Mac

#40
post #22
post #16

Is there any practical benefit of Podman over Docker on a Mac? Virtual machine is still needed, so any performance issues are likely to persist (well, maybe Docker for Mac is a bit more buggy, but we can manually setup Docker instead of Podman in a similar way). Also, I think we are losing here access to the Docker socket on the host (inside the virtual machine it can be emulated using docker-podman).

Not having to pay Docker Inc to use it is the big advantage along with the security that comes with a solution that isn’t the meal ticket of the company that makes it so it will likely live on community supported for a long time.

What is podman’s revenue model?

I am perplexed by the conclusion that charging enterprise customers $5/user-month makes the product’s future less secure.

Post reply on HN