Skip to content

Add CI workflow for statically linked bwrap release binaries - #823

Closed
luiarthur wants to merge 4 commits into
containers:mainfrom
luiarthur:main
Closed

luiarthur wants to merge 4 commits into
containers:mainfrom
luiarthur:main

Conversation

@luiarthur

@luiarthur luiarthur commented Oct 26, 2026 •

Copy link
Copy Markdown

Hi,

This PR adds a GitHub Actions workflow that builds statically linked bwrap binaries for Linux aarch64 and x86_64 using Alpine Linux (alpine:3.23).

After downloading the binary, set execution bit first before running. E.g.,

chmod +x bwrap-$(arch)
ln -s bwrap-$(arch) bwrap
./bwrap --version

Signed-off-by: Arthur Lui <alui@lanl.gov>
Signed-off-by: Arthur Lui <alui@lanl.gov>
Signed-off-by: Arthur Lui <alui@lanl.gov>
Signed-off-by: Arthur Lui <alui@lanl.gov>
@smcv

smcv commented Oct 26, 2026

Copy link
Copy Markdown
Collaborator

The bubblewrap maintainers already have insufficient time to do everything we are trying to be responsible for. I don't think we want to be in the business of releasing ready-to-use binaries, which will create an expectation that we are responsible for end-user technical support, security fixes and so on.

OS distributions are already good at releasing binaries and (at least in the better OS distributions!) handling security updates, and the bubblewrap binaries that get used in production should often come from them.

If you want to build your own bubblewrap binaries from CI and take responsibility for their quality and security, that's already something you could do.

@smcv smcv closed this Oct 26, 2026
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.

2 participants