While installing Docker, I see this message: * Checking for suitable kernel configuration options... * CONFIG_RT_GROUP_SCHED: is not set when it should be. This is probably wrong, and breaks RT scheduling without further configuration. E.g.: rtkit-daemon[3766]: Failed to make ourselves RT: Operation not permitted See https://bugzilla.redhat.com/show_bug.cgi?id=1229700 for further explanation. Disabling CONFIG_RT_GROUP_SCHED solved the rtkit problem for me.
I was a bit surprised to see this pop up as well. If you enable this you will get this rom other builds: CONFIG_RT_GROUP_SCHED is enabled. rtkit-daemon (or any other real-time task) will not work unless run as root. Please consider unsetting this option. This leads to ambiguity in whether to turn it on or off. Off seems the better option.
This has been fixed for a while, so I'm closing the bug.
I just emerged app-emulation/docker-19.03.14 and still got the same message: * Messages for package app-emulation/docker-19.03.14: * CONFIG_RT_GROUP_SCHED: is not set when it should be. * Please check to make sure these options are set correctly. * Failure to do so may cause unexpected problems. It's still in the ebuild (https://github.com/gentoo/gentoo/blob/49a881ac2c9c2725ae8f869afea1fe932f97b1ac/app-emulation/docker/docker-19.03.14.ebuild#L88) so doesn't seem fixed?
No, it isn't fixed. The newest ebuild still has this check.
Ping.
>>> Emerging (1 of 1) app-emulation/docker-19.03.15::gentoo * docker-19.03.15.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 5.11.8-gentoo-r1 * Checking for suitable kernel configuration options... * CONFIG_CFS_BANDWIDTH: is optional for container statistics gathering * CONFIG_RT_GROUP_SCHED: is not set when it should be. * Please check to make sure these options are set correctly. * Failure to do so may cause unexpected problems.
is there any way to skip enabling CONFIG_RT_GROUP_SCHED?
4 years later, I'm going to call a maintainer timeout here.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fc8e746b01faa624dc3b059f0dbe7baaffb06700 commit fc8e746b01faa624dc3b059f0dbe7baaffb06700 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2021-03-25 07:22:28 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2021-03-25 08:02:00 +0000 app-emulation/docker: Remove CONFIG_RT_GROUP_SCHED Closes: https://bugs.gentoo.org/606548 Signed-off-by: Michał Górny <mgorny@gentoo.org> app-emulation/docker/docker-19.03.15.ebuild | 2 +- app-emulation/docker/docker-20.10.3-r2.ebuild | 2 +- app-emulation/docker/docker-20.10.4.ebuild | 2 +- app-emulation/docker/docker-20.10.5.ebuild | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-)
The check and error are back in docker-23.0.1: https://gitweb.gentoo.org/repo/gentoo.git/tree/app-containers/docker/docker-23.0.1.ebuild#n162
This bug is present again in Docker 23.0.3: >>> Emerging (6 of 11) app-containers/docker-23.0.3::gentoo * docker-23.0.3.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 6.1.19-gentoo-x86_64-Custom * Checking for suitable kernel configuration options ... * CONFIG_RT_GROUP_SCHED: is not set when it should be. [ !! ] * Please check to make sure these options are set correctly. * Failure to do so may cause unexpected problems.
Docker would run without CONFIG_RT_GROUP_SCHED?
Yes it would. It's actually problematic to enable it for many cases. Especially the "docker on my personal workstation" use case.
