Live data from Hacker News

Podman, the open source Docker alternative ported to M1 (Apple Silicon) machines

github.com

51–60 of 151 posts

Re: Podman, the open source Docker alternative ported to M1 (Apple Silicon) machines

#52

Earlier quoted context omitted.

We don't know anything for sure, only rumors: https://www.macrumors.com/guide/14-inch-macbook-pro/

Thank you. This answer all the questions except the Pro-vs-Air difference.

The current macbook pro 13 with M1 does not differ significantly from the macbook air m1: https://9to5mac.com/2021/09/01/m1-macbook-air-vs-m1-macbook-... . You have one core more and active cooling with fan, but in daily use it is difficult to generate the load that will trigger this cooling. The situation will definitely change with the new Macbook Pro 14/16 to be shown in October or November.

Re: Podman, the open source Docker alternative ported to M1 (Apple Silicon) machines

#53
post #25

Earlier quoted context omitted.

I think a really big part of it was where Red Hat asked Docker to accept their patch that allowed people to run docker with local registries only (no docker.io), and were told Docker would not be accepting that patch, and to go pound sand if they didn't like it (eh, so maybe not so forcefully). The first thing I tried to figure out when looking into Docker for work was how to limit the registries it would look at to…

Fascinating history, is there a PR link for this exchange between Redhat and Docker?

https://github.com/moby/moby/issues/1988#issuecomment-271402...

Re: Podman, the open source Docker alternative ported to M1 (Apple Silicon) machines

#54
post #25

Earlier quoted context omitted.

I suspect the push for podman was more about how docker ignored CGroupsV2 for so long that Fedora eventually turned it on anyway which broke docker and then told users to switch to podman.

I think a really big part of it was where Red Hat asked Docker to accept their patch that allowed people to run docker with local registries only (no docker.io), and were told Docker would not be accepting that patch, and to go pound sand if they didn't like it (eh, so maybe not so forcefully). The first thing I tried to figure out when looking into Docker for work was how to limit the registries it would look at to…

Docker does this a lot. For example, we were trying to turn off gzipping images on the wire when pulling because it actually cost more when done from the intranet.

You can't. And modifying the source was so convoluted that we gave up.

Then we needed to clean up docker (before there were commands to do that) when it started to eat up all of the disk space.

To our (un)surprise, Docker uses 3 (!!) different storage formats, many of them having redundant information, and editing one of them would cause the other to be corrupted.

One was a binary database format that was specific to Go and didn't have any utility CLI to work with, so you had to write a programmatic interface with it just to edit it.

Or how about the fact that even if you issue commands directly to docker over the HTTP Unix socket, it will deadlock if you issue too many commands to it? This became our nightmare when trying to implement one of the first iterations of custom deployment backends at ZEIT. In fact, the entire project failed because of docker (there was no great alternative at the time).

Re: Podman, the open source Docker alternative ported to M1 (Apple Silicon) machines

#56
post #44
post #39

Earlier quoted context omitted.

... sure seems like it is: this handles QEMU setup/teardown with hardware virtualization support through Hypervisor.framework according to[0]. [0] https://twitter.com/simnalamburt/status/1434244533001224192

Doesn't Docker proper do that on Mac?

AFAIK the Docker engine (that allows to run containers) isn't available for Mac independently of Docker Desktop.

At least binaries are not provided. https://docs.docker.com/engine/install/binaries/

Re: Podman, the open source Docker alternative ported to M1 (Apple Silicon) machines

#57
post #56
post #44

Earlier quoted context omitted.

Doesn't Docker proper do that on Mac?

AFAIK the Docker engine (that allows to run containers) isn't available for Mac independently of Docker Desktop. At least binaries are not provided. https://docs.docker.com/engine/install/binaries/

Oh wow, really? I thought Docker Desktop was only a UI that helped you start/stop Docker, I didn't realize there's no OSS version at all. That's much worse than I thought, wow.

I guess I'll have to switch to Podman too, even though I don't use Mac, just because we need a unified approach across OSes in our company and can't afford to have Mac-using developers be second-class citizens.

Re: Podman, the open source Docker alternative ported to M1 (Apple Silicon) machines

#58
post #43
post #29

Calling podman “the open-source docker alternative” is disingenuous. The Docker engine which it competes with is also open-source. The only closed Docker product is their desktop wrapper, for which podman is not an alternative. Podman people, you’re better than this.

Docker is open-core.

Docker Desktop is not

Re: Podman, the open source Docker alternative ported to M1 (Apple Silicon) machines

#59
post #46
post #31

Earlier quoted context omitted.

Does that handle virtualization for you like this does? Is it distributed pre-built anywhere? I honestly looked just now and couldn't find anything.

I would be surprised if it didn't, as Docker wouldn't work at all then.

It doesn't.

That is part of the "Docker Desktop" offer, which is non-free.

Re: Podman, the open source Docker alternative ported to M1 (Apple Silicon) machines

#60
post #59
post #46

Earlier quoted context omitted.

I would be surprised if it didn't, as Docker wouldn't work at all then.

It doesn't. That is part of the "Docker Desktop" offer, which is non-free.

I just heard (from another commenter), that's dire. I'm stunned.
Post reply on HN