On 24 May 2022, at 12:58, Clemens Eisserer <linuxhippy@xxxxxxxxx> wrote:
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.
Containers have be run with selinux in the same mode as used to create them.Did you create the contain with selinux enabled?
I hit this issue and it had very confusing error messages. Folks on the pod and list helped diagnose this in my case.
Barry
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
|
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
