I noticed in the documentation it says non Linux as an option. Is anyone using podman to run Windows containers? If so, have you written it up? I've exported a bunch of containers from Google Cloud to run on virtual box but it's clunky and doesn't always work.
Migrating from Docker to Podman
71–80 of 111 posts
Re: Migrating from Docker to Podman
#72I see all comments here and I’m wondering if anybody actually read TFA. This is NOT a drop-in replacement on Mac, very far from it. No volumes mount from the host, no auto port forward, complications when building images, bugs where the socket isn’t cleared etc. They will get there eventually but this is way over hyped for a sensible replacement for docker on Mac.
> They will get there eventually but this is way over hyped for a sensible replacement for docker on Mac.
The nice thing is that even if it's not useful for you on your development system, your Docker work will still run on it the exact same elsewhere where it does work (hopefully).
There is a somewhat recent article from Red Hat on how to get it working on a Mac[1], but it seems somewhat convoluted in that a lot of stuff (virtualization) that Docker for the Mac apparently does for you is not automated yet.
Edit: Oh, I guess this announcement for 3.3.0 is more/better non-unix support? Is that the version you tried? Maybe they made some of this easier.
1: https://www.redhat.com/sysadmin/replace-docker-podman-macos
Re: Migrating from Docker to Podman
#73I see all comments here and I’m wondering if anybody actually read TFA. This is NOT a drop-in replacement on Mac, very far from it. No volumes mount from the host, no auto port forward, complications when building images, bugs where the socket isn’t cleared etc. They will get there eventually but this is way over hyped for a sensible replacement for docker on Mac.
Seems like the majority of responses I get when I ask about Mac support is "why don't you just run Linux?"
I do, but not for my workstation, where I do media production and a lot of other things that require a GUI and I use software that, unfortunately, doesn't run as well on Linux (if at all).
I have plenty of Linux servers, but if I wanted to do all my development work 'over the wire' I wouldn't use Docker Desktop either.
Re: Migrating from Docker to Podman
#74Shameless plug: I wrote undocker[1] to convert docker images to a rootfs tarball, so I can run them with plain systemd. Goal: no more daemons to run 3rd party containers, systemd is good enough by now: resource limits, isolation, chroot, dynamic users, logging, and more. Low-level tooling is done, I am now building ecosystem around it: easy installation, convert to deb/rpm, systemd units, etc. [1]: https://sr.ht/~mot…
[deleted]
Re: Migrating from Docker to Podman
#75How does podman replace docker desktop? I thought it more as an alternative to the docker daemon, which is still free and open source. I start to wonder if people actually value open source if they run away from something just because some company publishes a commercial GUI. I like that with docker swarm one can without too much headache go from dev environments to a cluster. At university this seems much better than…
podman has a `machine` subcommand for setting up a VM for running podman. It configures the podman server and your podman client connects to the server, very much like docker.
https://docs.podman.io/en/latest/markdown/podman-machine.1.h...
Re: Migrating from Docker to Podman
#76Earlier quoted context omitted.
That actually looks pretty interesting. How do you handle load balancing of inbound traffic.. do you use a pod running Traefik or similar? How do the pods communicate when they are deploying, unavailable or busy and so on? I guess I could get this from your site but there's a LOT of information on the first pages there and possibly not what I am looking for.
Thanks, We use haproxy pods for inbound traffic, they perform TLS termination and simply pass the traffic over to a local proxy pod. The haproxy pod (and all other pods) communicate with each other over this local proxy service which is running on each host. We have a very simplified and robust overall architecture, were each pod allocates a specific virtual port and the proxy will try each host for that pod (and rem…
Ok thanks. Interesting approach. I guess it would be interesting to see how easy something is to troubleshoot, should something actually go wrong.
Re: Migrating from Docker to Podman
#77Earlier quoted context omitted.
I just found out about Docker's rootless mode in an HN thread the other day. The docs make it seem simple, with few meaningful limitations. Really interested to hear some more about the additional setup you needed to do, and what behavioural differences you've encountered?
It's a colossal pain in the ass to get working. They recommend using Ubuntu. And they are not joking. Just click on the other distros to see the amount of hoops you have to jump through. You can't even get overlay2, which offers the best filesystem performance. Not to mention the benchmarks I've seen have slirp4netns at about ~3% of the performance of root veth. I would consider both of those incredibly meaningful li…
podman's rootless suffers from the same performance issues as docker's.
This is all the same exact tech.
Rootful- is always going to be smoother to get working. Docker can be a lot smoother than it is today, though.
Re: Migrating from Docker to Podman
#78Earlier quoted context omitted.
Podman [supports][1] `docker-compose` now. Just set `DOCKER_HOST` to the path of your Podman socket after activating the service, and it should just work (unless you use Swarm, which is not supported). [1]: https://www.redhat.com/sysadmin/podman-docker-compose
Thanks for the heads up. It's worth noting for others that (it appears from a quick read, I haven't actually used this yet), the compromise for gaining the "docker-compose" superpower is that you will have to run a podman service (Daemon). This comes counter to some (not all) of the benefits I mentioned above, but is a necessary compromise if one wants the power of compose style orchestration; that is, that there mus…
The Podman daemon can run as a user service, so the only advantage that would be lost is not having to run a daemon at all (but I don’t think one can avoid that if Docker API compatibility is needed). Is there something else I’m not considering?
Re: Migrating from Docker to Podman
#79Shameless plug: I wrote undocker[1] to convert docker images to a rootfs tarball, so I can run them with plain systemd. Goal: no more daemons to run 3rd party containers, systemd is good enough by now: resource limits, isolation, chroot, dynamic users, logging, and more. Low-level tooling is done, I am now building ecosystem around it: easy installation, convert to deb/rpm, systemd units, etc. [1]: https://sr.ht/~mot…
I love your project!
Can I still get the same networking functionality with undocker/systemd that docker provides? For example, container hostname resolution, private networks, container->localhost port forwarding?
Re: Migrating from Docker to Podman
#80Earlier quoted context omitted.
you're right. And the caveat is still that Docker Desktop costs $240 a year only for companies with $10m+ in revenue or 250+ employees. Free for everyone else. I don't get the whole "Let's spend weeks rewriting our build infrastructure to save $240 a year" strategy going on here.
$240 a year * 250+ employees is 60k at the very least. My company has over 3500 engineers. That's almost a million dollars in new spend and you gain basically nothing. It's a product the entire org has already been using for a long time, now you just have to pay a million dollars a year to use it.
You gain support. And the continued existence of the company that developed Docker CLI & GUI. Surely that’s important to your 3500 engineer company’s future too?