How to Replace Docker with Podman on a Mac • Hacker News Board

Re: How to Replace Docker with Podman on a Mac

#21

Post by jagger27 » Wed, Sep 08, 2021, 10:06 PM UTC

arthurcolle wrote: post #18

williamsmj wrote: post #9

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

It more or less works, at least on Linux.

https://www.redhat.com/sysadmin/podman-docker-compose

Re: How to Replace Docker with Podman on a Mac

#22

Post by Spivak » Wed, Sep 08, 2021, 10:07 PM UTC

suchar wrote: 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.

Re: How to Replace Docker with Podman on a Mac

#23

Post by tambourine_man » Wed, Sep 08, 2021, 10:11 PM UTC

Is Vagrant still actively used? I was all over it some 4-5 years ago.

I remember HashiCorp even favoring a newer product they were trying to promote.

Re: How to Replace Docker with Podman on a Mac

#24

Post by gizdan » Wed, Sep 08, 2021, 10:12 PM UTC

suchar wrote: 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).

Podman does have a socket that can be started. I use it on Linux so I'm not sure how that works on MacOS but it's API is Docker compatible, thus works with the docker cli and docker-compose as well.

Re: How to Replace Docker with Podman on a Mac

#25

Post by gizdan » Wed, Sep 08, 2021, 10:13 PM UTC

cpitman wrote: post #4

conceptme wrote: post #3

Earlier quoted context omitted.

It is mentioned in the article. "Fast forward a couple of months, podman-machine is now deprecated in lieu of Vagrant"

That's not accurate. There was an older project called podman-machine, which is long gone. What you get when you use the `podman machine` command is a completely new implementation.

And it is built into the podman binary, as opposed to being a separate project.

Re: How to Replace Docker with Podman on a Mac

#26

Post by demarq » Wed, Sep 08, 2021, 10:14 PM UTC

suchar wrote: 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).

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

Re: How to Replace Docker with Podman on a Mac

#27

Post by jagger27 » Wed, Sep 08, 2021, 10:17 PM UTC

swlkr wrote: 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.

Re: How to Replace Docker with Podman on a Mac

#28

Post by haberman » Wed, Sep 08, 2021, 10:27 PM UTC

jagger27 wrote: post #27

swlkr wrote: 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.

I've run into this too. My solution was to add some code in entrypoint.sh that looks for the UID/GID of mounted files, then creates a group and user to match. We can then exec the real command as that user.

Re: How to Replace Docker with Podman on a Mac

#29

Post by while1fork » Wed, Sep 08, 2021, 10:30 PM UTC

I replaced docker desktop on my Mac with the CLI brew version and set DOCKER_HOST. This is because my 96-core, 0.5 TB RAM Linux server can run it just a wee bit faster than an old Mac mini.

Re: How to Replace Docker with Podman on a Mac

#30

Post by tjscott » Wed, Sep 08, 2021, 10:36 PM UTC

demarq wrote: post #26

suchar wrote: 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).

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 awful experience on Mac for a long time, so any competition is surely welcome.

[1] https://github.com/docker/for-mac/issues/3499