Skip to content

chore: remove unused bwrap binary from Docker image#244

Merged
mbabic84 merged 1 commit into
mainfrom
chore/remove-unused-bwrap
Jul 12, 2026
Merged

chore: remove unused bwrap binary from Docker image#244
mbabic84 merged 1 commit into
mainfrom
chore/remove-unused-bwrap

Conversation

@mbabic84

Copy link
Copy Markdown
Owner

Summary

Remove unused Bubblewrap (bwrap) binary from Docker image.

Problem

The bwrap binary was added in v3.49.0 (PR #243) to support Kilo CLI's sandbox feature. However, sandbox functionality is redundant inside Docker containers because:

  1. Docker already provides isolation — Containers use Linux namespaces (PID, network, mount, UTS, IPC), cgroups, and capability restrictions
  2. bwrap requires weakening Docker — Running bwrap inside a container requires --privileged or --cap-add SYS_ADMIN, which removes Docker's own security protections
  3. Often doesn't work — Without elevated privileges, bwrap fails immediately due to namespace restrictions

Changes

  • Dockerfile — Removed COPY --from=builder /tmp/bwrap /usr/local/bin/bwrap line

Verification

  • go build ./...
  • go test ./...
  • go vet ./...

Bubblewrap (bwrap) sandbox is redundant inside Docker containers.
Docker already provides namespace isolation, and running bwrap inside
a container requires --privileged which weakens Docker's security model.

The bwrap binary was added in v3.49.0 but serves no purpose in the
containerized deployment.
@mbabic84
mbabic84 merged commit 4a01d82 into main Jul 12, 2026
1 check passed
@mbabic84
mbabic84 deleted the chore/remove-unused-bwrap branch July 12, 2026 14:21
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 3.49.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant