Repository navigation
ci: let bwrap create user namespaces on the runner so the sandbox test runs - #1209
Merged
Merged
Conversation
…t runs bwrap failed with "setting up uid map: Permission denied": Ubuntu 24.04 runners block unprivileged user namespaces through AppArmor. The sandbox test skipped for that reason, so its check never ran. The setting is relaxed on the CI VM only, in the test job, and the temporary diagnostics step is removed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #1207
Diagnosis
The diagnostics run (#1208) showed the cause on the runner:
Ubuntu 24.04 blocks unprivileged user namespaces through AppArmor, so bwrap cannot start, and the sandbox test skipped with "bwrap is not usable here".
Change
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0. The setting applies to the CI VM only; the shipped app is not affected.Risk to watch
If the sandbox test now runs and fails, the sandbox lets a write reach the host. That is a finding to fix, not a reason to skip the test again.