besoeasy/airlock
besoeasy/airlock has 109 GitHub stars and 54 forks. GitHot measured 0 stars in 24 hours and +1 in 7 days. Last checked 2026-11-16 19:39 UTC. Last push 2026-10-26.
What you can do
- 26 preconfigured runtimes across programming languages, Linux distributions, security tools, and AI coding agents.
- Disposable by default — containers are removed automatically when you exit.
- Live workspace mounting — edit the same files from the host and container in real time.
- Project configuration — define runtimes, ports, environment variables, and setup commands in .airlock.
Measured star growth
- in 24h
- 0
- in 7 days
- +1
- in 15 days
- Collecting history
- in 1 month
- Collecting history
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
About
Run multiple AI agents and untrusted code in isolation. One command spins up a disposable Podman container — your SSH keys, dotfiles, and env files stay safe.
AIREADME.md
Original
Airlock
Instant, disposable development environments and sandboxes.
Run, build, scan, and test code without cluttering or putting your host machine at risk.
Introduction
Airlock puts your project inside a preconfigured rootless Podman container. Your working directory stays available at /workspace, while toolchains, packages, and other changes outside the workspace disappear with the container.
Use a throwaway sandbox for one-off builds and scans, or create a persistent devbox when you want to keep your environment between sessions. Airlock supports Linux, macOS, and WSL2.
Install
Install Airlock and its container engine with one command:
curl -fsSL https://cdn.jsdelivr.net/gh/besoeasy/airlock@main/install.sh | bash
The installer adds airlock to your PATH and installs Podman when needed. Re-run the same command whenever you want to update Airlock.
Usage
Launch an environment for your project:
cd my-project
airlock
With no .airlock file, running airlock opens an interactive menu where you can choose a runtime instead.
Why We Built Airlock
Installing every SDK, scanner, and test tool on your host machine is slow, difficult to reproduce, and easy to pollute. Running unfamiliar project scripts with your normal user account is also risky.
Airlock gives you a clean environment on demand: launch the tools you need, keep your source mounted in place, and throw the rest away when you are done. When a longer-lived setup is useful, a persistent devbox provides the same isolation without the cleanup.
Features
- 26 preconfigured runtimes across programming languages, Linux distributions, security tools, and AI coding agents.
- Disposable by default — containers are removed automatically when you exit.
- Live workspace mounting — edit the same files from the host and container in real time.
- Project configuration — define runtimes, ports, environment variables, and setup commands in
.airlock. - Persistent devboxes — keep packages and configuration across multiple sessions.
- Rootless and security-conscious — uses rootless Podman, automatic SELinux relabeling, and process limits.
- Dependency-free CLI — one Bash script with no framework or third-party runtime required.
Documentation
| Guide | What it covers |
|---|---|
| CLI Reference | Commands, options, aliases, examples, and shell completions |
| Supported Runtimes | Available languages, distributions, tools, and scanner behavior |
| Project Configuration | .airlock keys, lifecycle hooks, and port configuration |
| Persistent Devboxes | Creating, entering, listing, and deleting long-lived environments |
| Platforms & Security | Host support, Podman setup, SELinux, macOS, and WSL2 |
| Airlock vs Toolbox | Comparing disposable and persistent container workflows |