Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

syscall: installing Go in chroot chronically fails on TestCloneNEWUSERAndRemapRootDisableSetgroups if /proc/sys/kernel/unprivilged_userns_clone is not 1 #34178

Open
Ulmo opened this issue Sep 8, 2019 · 1 comment
Open

syscall: installing Go in chroot chronically fails on TestCloneNEWUSERAndRemapRootDisableSetgroups if /proc/sys/kernel/unprivilged_userns_clone is not 1 #34178

Ulmo opened this issue Sep 8, 2019 · 1 comment
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsFix The path to resolution is known, but the work has not been done. OS-Linux
Milestone
Backlog

Comments

@Ulmo
Copy link

Ulmo commented Sep 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.
@odeke-em 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 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
@odeke-em
Copy link
Member

odeke-em commented Sep 8, 2019

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.
Kindly pinging perhaps some interested parties @LK4D4 @ianlancetaylor @ALTree.

@odeke-em odeke-em added OS-Linux NeedsFix The path to resolution is known, but the work has not been done. labels Sep 8, 2019
@odeke-em odeke-em added this to the Go1.14 milestone Sep 8, 2019
@rsc rsc modified the milestones: Go1.14, Backlog Oct 9, 2019
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jul 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsFix The path to resolution is known, but the work has not been done. OS-Linux
Projects
Go Compiler / Runtime
Status: Triage Backlog
Milestone
Backlog
Development

No branches or pull requests
4 participants
@rsc @Ulmo @odeke-em @gopherbot