HI there, I've just recently upgraded from F35->F36 and now podman containers don't start anymore. When starting a container which was created with F35 as user, I just get: Error: OCI runtime error: unable to start container "0a4d835ccc0777ccf77bc61976c32d9c3fbbf32c18902f0a2043a0 12d5fed598": runc: runc create failed: unable to start container process: can't get final child's PID from pipe: EOF It is a bit unfortunate I need the containers as they are, so I can't simply recreate them. I've tried to solve the problem by installing crun and making sure runc is installed, however nothing helped- Any idea what could be the problem? Thank you in advance, Clemens _______________________________________________ users mailing list --users(a)lists.fedoraproject.org To unsubscribe send an email tousers-leave(a)lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedora... Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure

Hi Daniel, Thanks for your hint :) Are you seeing the SELinux AVC error?  Does this work if you put your machine into permissive mode? I am running with SELINUX=disabled, so I guess this is not caused by selinux. I've now discarded all the old containers that were not able to start - however it is a bit unfortunate, the error message was so useless in debugging the root cause. I really tried searching on various mailing list archives for ~2 hours and that error seems completly ambigous with many causes. Thanks & best regards, Clemens