Live data from Hacker News

How to Replace Docker with Podman on a Mac

redhat.com

81–90 of 90 posts

Re: How to Replace Docker with Podman on a Mac

#81
post #47

Earlier quoted context omitted.

Networking is working just fine over here; I rebuilt the machine to be using the latest (Sept 4) FCOS stream, but it was fine on the previous version (Aug 21) as well. Are you using short names to pull your images, i.e. 'requarks/wiki:latest' rather than the full path 'docker.io/requarks/wiki:latest'? (Note: official images in Docker Hub are under the 'library/' namespace, e.g. 'library/fedora') Other networking issu…

One issue still apparently is that it can’t mount volumes. Though I haven’t had to do that yet. When you attempt to mount a volume it will attempt to do it from within the virtual machine not your machine.

This is a known issue and is in the process of being figure out how to proceed: https://github.com/containers/podman/issues/8016

Re: How to Replace Docker with Podman on a Mac

#82
post #64
post #37

Earlier quoted context omitted.

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

I'm happy your platform of choice has no bugs nor quirks. Could you let us know which one it is? We can probably help you find the bullshit you put up with that has become second nature.

I'm not the one claiming my system is the perfect dev machine.

Re: How to Replace Docker with Podman on a Mac

#83
post #82
post #64

Earlier quoted context omitted.

I'm happy your platform of choice has no bugs nor quirks. Could you let us know which one it is? We can probably help you find the bullshit you put up with that has become second nature.

I'm not the one claiming my system is the perfect dev machine.

Plenty of Apple users complain about Apple, don’t just focus on the fanboys, which every platform has, even Windows.

Re: How to Replace Docker with Podman on a Mac

#84

Now there is `podman machine` which makes most of this article outdated.

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

See https://boot2podman.github.io/2020/07/05/boot2docker-depreca... for the reasons why Vagrant was/is a workaround, after docker-machine and podman-machine stopped working.

Re: How to Replace Docker with Podman on a Mac

#85

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"

I assume `podman-machine` is different than `podman machine` See Marcos install https://podman.io/getting-started/installation Also there are active issues and PR related to `podman machine`.

Yes, Red Hat reused the name - similar to the CoreOS name.

Re: How to Replace Docker with Podman on a Mac

#86

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"

So is a Vagrant-based alternative the current solution? Vagrant seems like it's long been a 'maintenance only' project for Hashicorp, though not abandoned at least.

Vagrant was a workaround, before the new project got off the ground: https://boot2podman.github.io/2020/07/22/machine-replacement...

Any virtualization solution could be used, with some more typing (like running the shell commands directly). It's not unique to Vagrant.

Re: How to Replace Docker with Podman on a Mac

#87
post #75

Earlier quoted context omitted.

The problem is that red hat wants to monetize on "the big stuff" that is enterprise level software with support, subscription and consulting. Docker Inc wants to monetize on the basic stuff (e.g. a dumb desktop UI)

Exactly, and lots of developers don't need a desktop UI. They just want something that sits in the background and gets out of their way.

Yep.

That's why docker inc is mostly failing and has to come up with this dumb stuff whereas red hat is thriving :)

Re: How to Replace Docker with Podman on a Mac

#88

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"

So is a Vagrant-based alternative the current solution? Vagrant seems like it's long been a 'maintenance only' project for Hashicorp, though not abandoned at least.

Lima is a new and better option for this, it does not use a bundled Ruby runtime and does not use anything from Oracle. Just Go and QEMU... See https://github.com/lima-vm/lima

Re: How to Replace Docker with Podman on a Mac

#89
post #47

Earlier quoted context omitted.

Networking is working just fine over here; I rebuilt the machine to be using the latest (Sept 4) FCOS stream, but it was fine on the previous version (Aug 21) as well. Are you using short names to pull your images, i.e. 'requarks/wiki:latest' rather than the full path 'docker.io/requarks/wiki:latest'? (Note: official images in Docker Hub are under the 'library/' namespace, e.g. 'library/fedora') Other networking issu…

One issue still apparently is that it can’t mount volumes. Though I haven’t had to do that yet. When you attempt to mount a volume it will attempt to do it from within the virtual machine not your machine.

The issue to watch is here: https://github.com/containers/podman/issues/8016

To be clear volumes are supported, what aren't are "bind mounts" which are not recommended over named volumes: https://docs.docker.com/storage/volumes/ https://docs.docker.com/storage/bind-mounts/

Re: How to Replace Docker with Podman on a Mac

#90
post #51
post #24

Earlier quoted context omitted.

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.

IIRC the podman socket is a planned thing for macOS as it'll be necessary for certain features that rely on the docker socket and don't use SSH, such as VSCode's Remote Containers extension. However you can create an SSH tunnel to create the socket locally to allow non-podman clients to utilize the socket over SSH with the DOCKER_HOST environment variable. # Get URI > podman system connection ls # Create tunnel > ssh…

Socket location is wrong. Use this: export DOCKER_HOST='unix:///tmp/podman.sock'
Post reply on HN