Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upsyscall: installing Go in chroot chronically fails on TestCloneNEWUSERAndRemapRootDisableSetgroups if /proc/sys/kernel/unprivilged_userns_clone is not 1 #34178
Comments
odeke-em
changed the title
Repeat of closed locked issue #11261
syscall: installing Go in chroot chronically fails if /proc/sys/kernel/unprivilged_userns_clone is not 1
Sep 8, 2019
odeke-em
changed the title
syscall: installing Go in chroot chronically fails if /proc/sys/kernel/unprivilged_userns_clone is not 1
syscall: installing Go in chroot chronically fails on TestCloneNEWUSERAndRemapRootDisableSetgroups if /proc/sys/kernel/unprivilged_userns_clone is not 1
Sep 8, 2019
This comment has been minimized.
This comment has been minimized.
|
Thank you for this report @Ulmo and welcome to the Go project! I've updated the issue title accordingly and thanks for pointing out the remedy of your workaround. |
odeke-em
added
OS-Linux
NeedsFix
labels
Sep 8, 2019
odeke-em
added this to the Go1.14 milestone
Sep 8, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ulmo commentedSep 8, 2019
I'm installing the latest go in a chroot, and I'm getting a repeat of the error in #11261, but this time, the patch mentioned in #11261 (http://golang.org/cl/11269) doesn't stop the bug. I manually set that kernel variable (/proc/sys/kernel/unprivileged_userns_clone) to 0 rather than 1, and then the test succeeded, so that is a workaround, but the error still happened in the first place.
This workaround allowed Go to be installed successfully.
I am not going to repeat the data in #11261 since that already explained the background.