On Fri, Mar 11, 2022 at 2:51 AM Gabriel Filion <gabs...@lelutin.ca> wrote: > > Package: podman > Version: 3.4.4+ds1-1 > Severity: normal > > Hello, > > I used to be able to run rootless container on debian sid maybe 3 months ago > (I'm sorry, I don't have much more precise information about versions when > things used to work), but now that I try and start containers again I am > consistently hitting errors of this form: > > $ podman run -d --name="draw" -p 8080:8080 -p 8443:8443 fjudith/draw.io > Error: OCI runtime error: unable to start container > "0f2eb8afb9ce6eebbede769dc288e228ea6cbae0e76936672e6673228ac6862c": runc > create failed: unable to start container process: can't get final child's PID > from pipe: EOF >
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 -- Shengjing Zhu
