Several podman issues/requests
These results happen with a virtual machine running alpine edge.
Everything I did was apk add podman
and rc-update add cgroups
.
With that, podman 1.9.3 worked fine but rootless was broken due to uidmaps even after manually adding them.
With podman 2.0.0, it seems the config file got removed (afaik libpod.conf is deprecated in favor of containers.conf anyways?) which then makes sense. However, the default storage driver is now overlayfs, which requires adding a modules-load.d entry for overlay and then works. With podman run --rm -it --storage-driver=vfs docker.io/library/alpine:edge ash
it does work fine as root. Maybe it is possible to ship a modules-load.d entry?
My other concern is that I would like to use rootless and especially the 2.0 podman.sock as a drop-in replacement for docker.sock and from what I know, they ship systemd files. Can it be added as an openrc init script by any chance?
Finally, running rootless has uidmap issues as stated above. Without manual config I get this message:
If I add jens:231072:65536
(taken from my other machine with docker running) to both /etc/subuid and /etc/subgid, the warning before the pull disappears but the error when running stays. With the overlay module entry, I get a slirp4netns failure, which is resolved by adding tun
(and probably tap
) to the module load list. It then works fine from what I've experienced so far. But I feel like it could be less hacky?