$ brew install podman
$ podman machine init
$ podman machine start
$ alias docker=podman
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 issues, like the port publishing through the host bridging by default without needing to pass '--network' I believe are slated for the upcoming 3.3.2 patch release.
This is a known issue that also was present in the Docker for Apple Silicon public preview where they eventually fixed it by dropping built-in virtualization for qemu
I'll have to see if there's a Nix package for it tomorrow morning for work.
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).
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'
For example, a GUI program or even docker-compose.
However I must admit that I'm having serious troubles with podman+docker-compose (rhel 8.4, podman 3.2.3) so I reverted to podman-compose (which is way lower in quality and completeness).
It’s mind boggling to me how much HN refuses to pay (only for company licensing) for the innovation that is Docker, and would rather find alternatives to the tooling around it.
> solution that isn’t the meal ticket of the company
Usually I’ve seen arguments the other way around - X will do a good job /because/ it’s their core offering.
I am perplexed by the conclusion that charging enterprise customers $5/user-month makes the product’s future less secure.
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
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.
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…)
"Fast forward a couple of months, podman-machine is now deprecated in lieu of Vagrant"
See Marcos install https://podman.io/getting-started/installation
Also there are active issues and PR related to `podman machine`.
I need this volume mounting to get development code changes into the container in a reasonable time and the alternative performance feels like running on a standard hard drive compared to nvme ssd.
For devs who still have access to an Intel Mac, I personally would still use that over an M1 for container/VM/Linux tasks. We’re only a year into the transition so that’s OK, but don’t be caught off guard if you move to an M1 and find your stuff breaking. Incidentally, this is where I find stuff like GitHub Codespaces really nice because I can offload the container bits to a different machine.
I remember HashiCorp even favoring a newer product they were trying to promote.
https://man7.org/linux/man-pages/man2/mount_setattr.2.html#N...
Thanks redhat!
for example to see the last conatainer's logs:
podman logs -l
just beautiful!