Skip to content
This repository has been archived by the owner on Jan 1, 2021. It is now read-only.

CONFIG_NETPRIO_CGROUP was renamed in the kernel #47

Closed
samuelololol opened this issue Aug 19, 2015 · 3 comments
Closed

CONFIG_NETPRIO_CGROUP was renamed in the kernel #47

samuelololol opened this issue Aug 19, 2015 · 3 comments

Comments

@samuelololol
Copy link

There is an issue: moby/moby#15572 and it is fixed and closed.

While I am using docker-overlay to upgrade docker-1.7.1 to docker-1.8.1 with aufs-sources-4.1.5, docker package keeps complaining that the kernel setting is error. I think it is the same issue.

 *   CONFIG_NETPRIO_CGROUP:      is not set when it should be.
@tianon
Copy link
Owner

tianon commented Aug 19, 2015

Is your checkout of the overlay up to date? This should've been fixed by 694941c earlier today.

@samuelololol
Copy link
Author

What a coincidence! It's my bad.

After my sync with docker-overlay, another error happened.

>>> Emerging (1 of 1) app-emulation/docker-1.8.1::docker
 * docker-1.8.1.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ...                                                                                                                                                                            [ ok ]
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found kernel object directory:
 *     /lib/modules/4.1.5-aufs/build
 * Found sources for kernel version:
 *     4.1.5-aufs
 * Checking for suitable kernel configuration options...                                                                                                                                                                               [ ok ]
>>> Unpacking source...
>>> Source unpacked in /var/tmp/portage/app-emulation/docker-1.8.1/work
>>> Preparing source in /var/tmp/portage/app-emulation/docker-1.8.1/work/docker-1.8.1 ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-emulation/docker-1.8.1/work/docker-1.8.1 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/app-emulation/docker-1.8.1/work/docker-1.8.1 ...
/var/tmp/portage/app-emulation/docker-1.8.1/temp/environment: line 3259: ./hack/make.sh: No such file or directory
 * ERROR: app-emulation/docker-1.8.1::docker failed (compile phase):
 *   dynbinary failed
 * 
 * Call stack:
 *     ebuild.sh, line  93:  Called src_compile
 *   environment, line 3259:  Called die
 * The specific snippet of code:
 *       ./hack/make.sh dynbinary || die 'dynbinary failed'
 * 
 * If you need support, post the output of `emerge --info '=app-emulation/docker-1.8.1::docker'`,
 * the complete build log and the output of `emerge -pqv '=app-emulation/docker-1.8.1::docker'`.
 * The complete build log is located at '/var/tmp/portage/app-emulation/docker-1.8.1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-emulation/docker-1.8.1/temp/environment'.
 * Working directory: '/var/tmp/portage/app-emulation/docker-1.8.1/work/docker-1.8.1/src/github.com/docker/docker'
 * S: '/var/tmp/portage/app-emulation/docker-1.8.1/work/docker-1.8.1'

I am not sure what ./hack/make.sh: No such file or directory exactly means.
Do you need any further information?

@samuelololol
Copy link
Author

424577d now works!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants