Hi Shengjing,
On Sun, 19 Jun 2022 15:28:32 +0800 Shengjing Zhu <z...@debian.org> wrote:
> Can someone checks if you still fail to run rootless container with
> runc and podman 4.1?
>
> I think it's because
> https://github.com/containers/podman/issues/13731, which is fixed in
> podman 4.1.
> And it's caused by systemd 250 which changes OOMScoreAdjust in
user@.service
I just tried, and it seems that indeed, podman 4.1 fixes the issue. Here
are the steps I followed:
1) I removed the package crun, so that I only have runc installed:
$ sudo apt purge crun
2) From this point, I can reproduce the issue:
$ podman run --rm -it kali-rolling
Error: OCI runtime error: runc create failed: unable to start
container process: can't get final child's PID from pipe: EOF
3) Now I install podman from experimental:
$ sudo apt install -t experimental podman
Get:1 http://deb.debian.org/debian experimental/main amd64
golang-github-containers-common all 0.48.0+ds1-1 [34.5 kB]
Get:2 http://deb.debian.org/debian experimental/main amd64 podman
amd64 4.1.0+ds2-2 [9,997 kB]
Get:3 http://deb.debian.org/debian experimental/main amd64 buildah
amd64 1.26.1+ds1-1 [6,041 kB]
4) Tried to run podman rootless again:
$ podman run --rm -it kali-rolling
┌──(root㉿633e94a0ebde)-[/]
└─#
It works!
Thanks,
--
Arnaud Rebillout / Offensive Security / Kali Linux Developer
