podman

I don't see why you couldn't. One thing that I did not realize initially was that bind mounts do not work nicely out of the box on mac without mounting via sshfs. https://github.com/containers/podman/issues/8016

Podman also has a docker desktop alternative in the works (Already works on Mac IIRC)[0]. Will be interesting to see how these two solutions play out. 0: https://github.com/containers/podman/issues/11494

That does seem better! Of course, there are a few lingering issues with support, but overall the trend is good: https://github.com/containers/podman/issues?q=is%3Aissue+is%... Of course, there's no Swarm support, as evidenced by that very article: > Caveats > One known caveat is that Podman has not and will not implement the Swarm function. Therefore, if your Docker Compose instance uses Swarm, it will not work with Podman. Feels like people will either be pigeonholed into Kubernetes for all of their deployments, or will have to migrate over to something like Hashicorp Nomad: https://www.nomadproject.io/ Curiously, it also supports Podman as a task driver: https://www.nomadproject.io/docs/drivers/podman

the only issue really left is that volume mounts don't work with podman machine as of yet. The issue has been live on github for awhile, but its finally getting traction. Likely because of the recent Docker for Desktop changes. EDIT: github link: https://github.com/containers/podman/issues/8016

> root-less nature of podman I see this repeated a lot, but it's not the default, its has to be explicitly configured: https://github.com/containers/podman/blob/v3.3.1/docs/tutori... And in addition to the known upsides, there are some lesser known downsides: 1. There are feature limitations with it: https://github.com/containers/podman/blob/v3.3.1/rootless.md 2. There are security implications, quoting Arch Wiki: > Warning: Rootless Podman relies on the unprivileged user namespace usage (CONFIG_USER_NS_UNPRIVILEGED) which has some serious security implications, see Security#Sandboxing applications for details. Also worth noting that Docker itself has a rootless mode as well by now: https://docs.docker.com/engine/security/rootless/ I'm happy that there are Docker alternatives, but I have the feeling that podman has been hyped a lot recent

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/

I'm also looking forward to trying podman as an alternative to Docker Desktop for Mac, but it doesn't really do all the magic, yet. https://github.com/containers/podman/issues/11389

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

I tried podman on my MBP and didn't get very far :/ https://github.com/containers/podman/issues/11479

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 -nNT -L/tmp/podman.sock:/run/user/1000/podman/podman.sock -i ~/.ssh/podman-machine-default ssh://core@localhost:[PORT] # Export socket location > export DOCKER_HOST='/tmp/podman.sock' https://github.com/containers/podman/issues/11462 https://github.com/containers/podman/issues/11397

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/containers/podman/pull/11451).

Is anyone successfully using podman with docker-compose in the "locally remote" style that Docker Desktop makes simple? E.g. running `podman machine start` on a Mac, then `docker-compose up` to start all the containers in the current dir's `docker-compose.yml`, with mounts from the host and a default network. I'm following https://github.com/containers/podman/issues/11389 and https://github.com/containers/podman/issues/11397

I installed Podman 3.3.1 on a Mac yesterday from Homebrew and volume mounts were definitely an issue, but it otherwise worked as advertised on the command-line. The bugs cited in the article are already fixed in the code, so I don't hold those against it. I did have an issue that was my fault, encountered one genuine bug, and was disappointed to find that there's some work to be done before third-party tools can use it as a Docker replacement: https://github.com/containers/podman/issues/11397 I agree that Podman is not yet a complete replacement for Docker on macOS, but the experiment was successful enough for me that I intend to try Podman instead of Docker on Linux servers.

A recent example > $ podman start my_container > sd-bus call: Permission denied: OCI runtime permission denied error What on earth is an on OCI runtime? How are its permissions configured? Here's some issues with some random flags to configure: https://github.com/containers/podman/issues/6368 . How are these linked to podman? The devs know, where is this documented for Joe random user? Or another one I ran into: https://github.com/containers/podman/issues/7830 Again, here's some settings in files in /etc/containers to configure that might fix it? Where is this in the podman docs, or release notes? Just found my pods didn't start after an update one day and had to dig into github issues.

I'm not sure if it was you that downvoted me, but you are mistaken. boot2podman/machine, what you linked, is not an official part of podman. It is a third party equivalent and not relevant. The official podman repository is https://github.com/containers/podman, and the machine bits are integrated and part of podman proper: https://github.com/containers/podman/tree/main/cmd/podman/ma... If it was you that downvoted my comment, please consider not doing that because you disagree. The comment was factually correct and made in good faith. You're equating a third party deprecated podman-machine with the integrated into upstream podman machine. We were not referring to the same thing whatsoever. Hopefully this makes more sense to you now.