Live data from Hacker News

I ditched Docker for Podman

codesmash.dev

81–90 of 670 posts

Re: I ditched Docker for Podman

#81

One challenge I have come across is mapping multi-UID containers to a single host user. By default, root in the container maps to the user running the podman container on the host. Over the years, applications have adopted patterns where containers run as non-root users, for example www-data aka UID 33 (Debian) or just 1000. Those no longer map to your own user on the host, but subordinate IDs. I wish there was an ea…

If I understand things correctly, this is Linux namespaces limitation, so tools like Docker or Podman will not be able to support such mapping without support from Linux. But I'm afraid the requirement for UIDs to be mapped 1:1 is fundamental, otherwise, say two container users 1000 and 0 are mapped to the same host user 1000. Who then should be displayed in the container as the owner of a file that is owned by the user 1000 on a host?

Re: I ditched Docker for Podman

#82

I did numerous attempts to switch from docker to podman. Latest one worked, and so far I didn't feel the need to get back to docker. There was only one issue that I had: huge uid didn't work in podman (like 1000000 I think), but I fixed the dockerfile and rest worked fine for me. podman-compose does not work well in my experience, but I don't use it anymore.

Instead of using compose, you can create Kubernetes like yamls and run with podman play kube.

Of course if you have really large / complex compose files or just don't feel like learning something else / aren't using k8s, stick with docker.

Re: I ditched Docker for Podman

#83

Last third party container I’ve built had COPY —-link statements that didn’t worked on podman. Granted it worked just fine with a normal copy but it’s not 1:1.

Haven't tested this yet, but --link support was just added:

https://github.com/containers/buildah/issues/4325#issuecomme...

Re: I ditched Docker for Podman

#84
post #63

Earlier quoted context omitted.

Having an LLM function as a translation layer from docker compose to k8s yaml works really well. On another note, podman can generate k8s yaml for you, which is a nice touch and easy way to transition.

Use an LLM is not a solution. It's effectively telling you to switch your brain off and hope nothing goes wrong in the future. In reality things do go wrong and any conversation should be done with a good understanding of the system involved.

When things go wrong, you just ask the LLM about that too. It's 2025.

/s

Re: I ditched Docker for Podman

#86
post #8

I have ditched docker desktop on macOS for OrbStack.

OrbStack looks pretty nice, BUT an $8/mo/user subscription? Blech.

Orbstack is worth every penny. It's simply amazingly solid compared to Podman on macOS (a year ago at least, I don't know if Podman has improved). We migrated 100+ devs to Orbstack and it was like a collective sigh of relief that we finally had something that actually worked.

Re: I ditched Docker for Podman

#87

> If your Docker Compose workflow is overly complex, just convert it to Kubernetes YAML. We all use Kubernetes these days, so why even bother about this? I find that kubernetes yaml are a lot more complex than docker compose. And while I do, no, not everybody uses kubernetes.

I don't know how to create a compose file, but I do know how to create a k8s yaml. Therefore, compose is more "complex" for me.

Re: I ditched Docker for Podman

#88
post #38

Earlier quoted context omitted.

There's no need if all your devs use desktop Linux as their primary devices like we do where I work :)

On Mac we just switched to podman and didn't have anything to worry about.

Anyone have opinions on OrbStack for mac over these other alternatives?

Re: I ditched Docker for Podman

#89
post #2

Most of my containers end up on k8s clusters as pods. What else would one use podman or docker for beyond local dev or maybe running a local containerized service?

There are many SMB application use cases that sit somewhere on the spectrum between "self-hosted" and "enterprise" where docker/podman hit the sweet spot in terms of complexity and cost versus reliability. Containers have become a handy application packaging format (just don't tell yourself the isolation provides meaningful security on its own).

Re: I ditched Docker for Podman

#90
I had an issue where docker was not producing repeatable sha's. Somehow a time based metadata was affecting the image sha after every build.

Switching to podman immediately fixed it, never looked back

Post reply on HN