On 5/24/22 07:50, Clemens Eisserer 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.
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
Sorry this broke, I have no idea what could cause the issue, other then
SELinux upgrade issue. If you are running lots of containers in
production, I would really encourage you to enable SELinux, BTW.
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
