Skip to content

docs: Update README regarding setuid and user namespaces - #790

Closed
maruixin-kls wants to merge 1 commit into
containers:mainfrom
maruixin-kls:docs/update-setuid-readme
Closed

maruixin-kls wants to merge 1 commit into
containers:mainfrom
maruixin-kls:docs/update-setuid-readme

Conversation

@maruixin-kls

Copy link
Copy Markdown

Fixes #743

The README currently contains outdated information suggesting that setuid is the primary method for operation. This PR updates the text to clarify that bubblewrap now primarily relies on unprivileged user namespaces, aligning the documentation with the current implementation.

@smcv smcv left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, the paragraph you're deleting is still true, and is important contextual information.

Historically, bubblewrap did support being setuid root, and this has had a significant impact on its design. The fact that this is no longer available/supported doesn't change the fact that older versions of bubblewrap did have this behaviour.

In particular, this means that bubblewrap must continue to "fail closed" if someone mistakenly makes it setuid.

@smcv smcv closed this Sep 14, 2026
@smcv

smcv commented Sep 14, 2026

Copy link
Copy Markdown
Collaborator

#743 is specifically about the "Related project comparison: xxx" sections of the readme, which weren't altered by this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Related project comparisons in README.md are outdated

2 participants