Summary: | app-emulation/docker-1.4.1 should check for CONFIG_CPUSETS CONFIG_POSIX_MQUEUE | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dirk Best <mail> |
Component: | Current packages | Assignee: | Kacper Kowalik (Xarthisius) (RETIRED) <xarthisius> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | admwiggin, orzel, proxy-maint, xarthisius |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dirk Best
2015-01-14 04:45:08 UTC
Our kernel requirements come directly from upstream's "config/check-config.sh" script (https://github.com/docker/docker/blob/973c32c8a07bca01aa5889689f37b99694673490/contrib/check-config.sh). I recently resynced docker-9999.ebuild in the docker-overlay to the latest which included CONFIG_POSIX_MQUEUE, but CONFIG_CPUSETS isn't in the upstream script. I think the next step here is to update the upstream script to check for CONFIG_CPUSETS as well, and then I'll happily add it into the ebuild from there. I confirm, i've had the problem today. Containers wouldn't start with the error "mountpoint for cpuset not found". I had CONFIG_CPUSETS disabled in the kernel. Once enabled, everything worked well. Indeed, this should be reported upstream for their (very useful) check script. Tianon - I agree that this is not checked by the upstream script[1] - but nevertheless it /does/ appear to be required. I'm testing docker-1.5.0 with the same results. Perhaps we could at least add an ewarn directing people to enable CONFIG_CPUSETS IF they see the error? [ Would have saved me some digging/head-scratching. ] [1] https://raw.githubusercontent.com/docker/docker/master/contrib/check-config.sh Would have saved me quite some time too. If upstream has fixed it, adding the test to the ebuild would be a kind of bugfix backport. Makes sense, no ? Filed upstream: https://github.com/docker/docker/pull/11374 And it's already done, reviewed and even merged ! Updated in the overlay, will be in docker-1.6.0.ebuild for sure. I've leave it up to xarthisius whether he thinks we should sync this change to 1.5.0 in tree. :) + 14 Mar 2015; Kacper Kowalik <xarthisius@gentoo.org> docker-1.5.0.ebuild: + Check if CPUSETS are enabled in kernel wrt bug #536546 by Dirk Best <mail + @dirk-best.de>. Thanks to Tianon <admwiggin@gmail.com> for reporting and + fixing it upstream |