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…
I ditched Docker for Podman
91–100 of 670 posts
Re: I ditched Docker for Podman
#92You might expect that setting User=foo via systemd would enable seamless rootless containers, but it turns out to be a hard problem without a seamless solution.
Instead, there's this discussion thread with 86 comments and counting to wade through to find some solutions that have worked for some people in some cases.
https://github.com/containers/podman/discussions/20573#discu...
Re: I ditched Docker for Podman
#93Still happily using Colima as a Docker Desktop for Mac replacement. It even allows mixed architecture containers in the same compose stack. What's podman gain me besides a half baked Docker compose implementation?
If you use k8s for anything, podman might help you avoid remembering yet another iac format.
Re: I ditched Docker for Podman
#94- https://www.redhat.com/en/blog/user-namespaces-selinux-rootl... - https://www.redhat.com/en/blog/sudo-rootless-podman
I'd summarize these posts as "very carefully explaining how to solve insane problems."
Re: I ditched Docker for Podman
#95Earlier quoted context omitted.
Which actually makes a lot of sense, to hand over the orchestration / composing to systemd, since it’s not client server API calls (like with docker) anymore but actual userland processes.
It totally does! On the con side, I find systemd unit files a lot less ergonomic to work with than compose files that can easily be git-tracked and colocated.
Re: I ditched Docker for Podman
#96Earlier 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.
Re: I ditched Docker for Podman
#97Re: I ditched Docker for Podman
#98To bikeshed a little, "Why I Ditched Docker for Podman, And Why You Should Too" would be better than the current headline of "Why I Ditched Docker for Podman (And You Should Too)": the "you should too" part is after all the main message of the article, not a side-point.
Re: I ditched Docker for Podman
#99Earlier quoted context omitted.
None of your companies need to worry about licenses. Docker ENGINE is free and open source. Docker DESKTOP is a software suite that requires you to purchase a license to use in a company. But Docker Engine, the core component which works on Linux, Mac and Windows through WSL2, that is completely and 1000% free to use.
If you've installed Docker on Windows you've most likely done that by using Docker Desktop, though.
[1]: https://github.com/microsoft/winget-pkgs/tree/master/manifes...