4 ms·
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 th
by vbezhenar 1y ago
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.
- r_lee 1y agohave you tried nerdctl? its basically just the containerd cli which is close to k8s and etc. not a for profit thing, just following containerd spec
- wyoung2 1y ago> huge uid didn't work in podman (like 1000000 I think) You're running into the `/etc/sub[ug]id` defaults. The old default was to start your normal user at 100000 + 64k additional sub-IDs per user, but that changed recently when people at megacorps with hundreds of thousands of employees defined in LDAP and similar ran into ID conflict. Sub-IDs now start at 2^19 on RHEL10 for this reason.
- deleted 1y ago[deleted]
- osigurdson 1y agoInstead 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.