Leif Middelschulte <leif.middelschu...@gmail.com> added the comment:
@Christian Heimes: is there anything else you need from me? Is this the wrong forum? As discussed in the referenced GitHub issue, some SELinux people suggest it might be a fault in how Python determines (?) it's running within a container environment and how to act upon it. Does it determine it at all? Does it use libselinux[0]? Background: I came across this issue by building a Linux distribution using Yocto in a Fedora:30 podman managed container with host volumes bound in. I guess that it is a fairly common scenario in the near future. [0] https://danwalsh.livejournal.com/73099.html ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue38893> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
