Created attachment 655470 [details] emerge --info I noticed issues with some of my containers since upgrading libseccomp (I have tested 2.4.3 and 2.5.0). Originally it failed for my while installing glibc and I found this issue: https://github.com/moby/moby/issues/40734 The error shows up in different ways. When I try to start a mariadb service I get the following response and it's using 100% CPU # /etc/init.d/mysql restart * No permission to apply cgroup settings * Starting mysql ... * start-stop-daemon: nanosleep: Operation not permitted When I try to start a Java app in the container it also uses 100% CPU and I saw the following message: OpenJDK Client VM warning: No monotonic clock was available When I start a Python app I saw the following message: Fatal Python error: _Py_InitializeMainInterpreter: can't initialize time PermissionError: [Errno 1] Operation not permitted In case I start the container with the "--privileged" or the "--security-opt seccomp=unconfined" option, the applications/container are working without and issue.
Does this still happen with libseccomp-2.4.4 and/or libseccomp-2.5.1?
Thanks for following up. I can no longer reproduce the problem since I have update to the latest docker version (app-emulation/docker-19.03.13-r2). I'm still using sys-libs/libseccomp-2.4.3.
Marking this bug as obsolete because it's an issue with docker which seems to be fixed meanwhile.
