Open-Awesome
CategoriesAlternativesStacksSelf-HostedExplore
Open-Awesome

© 2026 Open-Awesome. Curated for the developer elite.

TermsPrivacyAboutGitHubRSS
  1. Home
  2. Containers
  3. Bubblewrap

Bubblewrap

NOASSERTIONCv0.11.2

A low-level unprivileged sandboxing tool for Linux that creates container-like environments without requiring root privileges.

GitHubGitHub
8.1k stars367 forks0 contributors

What is Bubblewrap?

Bubblewrap is a low-level sandboxing tool for Linux that allows unprivileged users to create isolated container environments without root access. It works by leveraging Linux namespaces and a setuid binary to construct secure, minimal sandboxes, addressing the security limitations of full user namespaces and privileged container runtimes. It serves as the foundational sandboxing layer for projects like Flatpak, enabling safe application execution.

Target Audience

Developers and system integrators building secure container frameworks or sandboxing solutions for Linux, particularly those working on desktop application distribution (like Flatpak) or unprivileged container tooling.

Value Proposition

Bubblewrap offers a minimal, auditable setuid sandboxing tool that avoids the security risks of full user namespaces, providing a reliable foundation for higher-level sandboxing frameworks without requiring root privileges.

Overview

Low-level unprivileged sandboxing tool used by Flatpak and similar projects

Use Cases

Best For

  • Creating secure sandboxes for desktop applications in frameworks like Flatpak
  • Building unprivileged container runtimes for Linux systems
  • Isolating processes with filesystem and namespace constraints without root access
  • Developing debugging tools for Kubernetes/OpenShift clusters with user-level container features
  • Implementing lightweight container environments for interactive scenarios
  • Sandboxing applications with custom security policies via seccomp and namespace controls

Not Ideal For

  • Developers wanting a complete, out-of-the-box sandbox with predefined security policies
  • Environments where unprivileged user namespaces are fully enabled and preferred over setuid tools
  • Projects requiring deep desktop integration like audio or GPU passthrough without additional frameworks
  • Teams unfamiliar with Linux namespace details and seccomp filter configuration

Pros & Cons

Pros

Unprivileged Sandboxing

Enables unprivileged users to create isolated containers without root access by using a setuid binary, addressing security risks of full user namespaces as noted in the README's discussion on CVE-2016-3135.

Minimal and Auditable

Focuses on a small codebase for core sandboxing, making it easier to security audit and maintain, as emphasized in the philosophy and comparisons with Firejail.

Comprehensive Namespace Support

Leverages Linux namespaces (user, IPC, PID, network, UTS) for robust isolation, including features like a tmpfs root and process reaping to avoid Docker pid 1 issues.

Security Hardening Features

Uses PR_SET_NO_NEW_PRIVS to disable setuid binaries and supports seccomp filters for syscall restrictions, enhancing sandbox security as described in the limitations section.

Cons

Configuration Complexity

Security is entirely dependent on command-line arguments, requiring deep expertise to avoid vulnerabilities like TIOCSTI exploits or improper mount bindings, as warned in the limitations.

Incomplete Sandbox Solution

Lacks built-in policies or desktop-specific features (e.g., Pulseaudio), necessitating integration with higher-level frameworks like Flatpak, which adds overhead.

Setuid Dependency Risks

Relies on a setuid binary, which, if flawed, could introduce privilege escalation risks, though the project claims it's secure; this contrasts with rootless runc that avoids setuid.

Limited Tooling Ecosystem

Compared to Docker or runc, it has fewer community tools and integrations, making it less suitable for orchestration or standalone container management without custom scripting.

Frequently Asked Questions

Quick Stats

Stars8,119
Forks367
Contributors0
Open Issues149
Last commit1 month ago
CreatedSince 2016

Tags

#container-runtime#filesystem-isolation#user-namespaces#security-hardening#linux-containers#unprivileged-containers#namespace-management

Built With

M
Meson

Included in

Containers2.0k
Auto-fetched 8 hours ago

Related Projects

NsJailNsJail

A lightweight process isolation tool that utilizes Linux namespaces, cgroups, rlimits and seccomp-bpf syscall filters, leveraging the Kafel BPF language for enhanced security.

Stars4,014
Forks348
Last commit1 month ago
singularitysingularity

Singularity has been renamed to Apptainer as part of us moving the project to the Linux Foundation. This repo has been persisted as a snapshot right before the changes.

Stars2,617
Forks425
Last commit3 years ago
SubuserSubuser

Run programs on linux with selectively restricted permissions.

Stars895
Forks63
Last commit1 year ago
LxrootLxroot

A lightweight, flexible, and safer alternative to chroot and/or Docker.

Stars121
Forks9
Last commit1 year ago
Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a projectStar on GitHub