How do I migrate from Docker to Devbox for development?

Start by creating a devbox.json file with your system packages, then use devbox shell for local isolation. Devbox can also generate Dockerfiles to align with existing container workflows, but it doesn't replace Docker for runtime environments.

Devbox vs Vagrant for development environments?

Devbox offers lighter-weight isolation using Nix shells without virtualization, making it faster for local use, while Vagrant provides full VM environments suitable for testing different OSes. Choose Devbox for speed and simplicity, Vagrant for OS-level reproducibility.

Does Devbox work on Windows?

The installation uses a curl script, which is Unix-centric; Windows support might require WSL or additional setup. Check the official Devbox documentation for specific instructions on Windows compatibility.

How to add custom or local packages to Devbox?

Use the devbox add command with package names from Nixhub.io, or refer to the docs for advanced configurations like overlays. However, it's limited to Nix-compatible packages, so fully custom builds may need Nix expertise.

Is Devbox good for production deployments?

Primarily designed for development, Devbox can generate Docker images for production, but it's not a deployment tool. For production, you'd typically export the environment to Docker and use orchestration tools like Kubernetes.

Can I use Devbox with existing shell configurations?

Yes, Devbox shells inherit your regular tools and environment variables, but specific configs might need adjustments. The README notes that git config and other settings are available, but complex setups could require additional scripting.

Open-Awesome

Devbox

Apache-2.0Go0.17.2

A command-line tool for creating isolated, reproducible development environments using Nix packages.

Visit Website GitHub

11.5k stars310 forks0 contributors

What is Devbox?

Devbox is a command-line tool that creates isolated development shells by defining system-level packages in a `devbox.json` file. It solves the problem of inconsistent tooling across teams and projects by providing reproducible environments using the Nix package manager.

Target Audience

Developers and teams working on multiple projects who need to manage different versions of system tools without conflicts, and DevOps engineers seeking reproducible development setups.

Value Proposition

Devbox offers a fast, easy-to-use interface to Nix, enabling isolated environments without virtualization overhead. It uniquely combines local shell isolation with portable environment definitions for containers and cloud development.

Overview

Instant, easy, and predictable development environments

Use Cases

Best For

Ensuring consistent tool versions across a development team
Experimenting with new tools without affecting your local machine
Managing multiple projects with conflicting dependency versions
Creating reproducible development environments for open-source contributions
Generating Docker images that match local development tools
Setting up remote development environments in the cloud

Not Ideal For

Projects requiring system packages not available in the Nix registry, such as proprietary or custom-built tools
Teams already using lightweight container workflows (e.g., Docker Compose) who don't need additional environment abstraction
Environments with strict IT policies that block Nix or curl-based installations
Use cases needing full OS virtualization or kernel-level isolation beyond user-space shells

Pros & Cons

Pros

Extensive Package Ecosystem

Accesses over 400,000 package versions from the Nix Package Registry, providing a vast selection of system-level tools without local installation.

No Virtualization Overhead

Runs directly on the machine without performance penalties from virtualization layers, making it faster than VM-based solutions like Docker for local development.

Portable Environment Definitions

A single devbox.json file can be used locally, in devcontainers, Docker images, or cloud setups, ensuring consistency across different environments as highlighted in the README.

Easy Nix Integration

Simplifies Nix usage by abstracting its complexity, allowing developers to create isolated shells with commands like devbox add without deep Nix expertise.

Cons

Nix Ecosystem Dependency

Relies entirely on the Nix package manager, which can be unfamiliar to developers and may involve compatibility issues or a steeper learning curve outside Devbox's abstraction.

Limited Package Availability

Only supports packages from the Nix registry, so projects needing tools not available there (e.g., certain proprietary software) cannot use Devbox effectively.

Setup and Maintenance Overhead

Requires initial installation via curl and ongoing management of Nix dependencies, which might be cumbersome in corporate environments or for teams resistant to new tooling.

Frequently Asked Questions

Related Projects

flox

The Deterministic Foundation for your SDLC

Stars3,915

Forks122

Last commit2 days ago

nix-direnv

A fast, persistent use_nix/use_flake implementation for direnv [maintainer=@Mic92 / @bbenne10]

Stars2,624

Forks143

Last commit5 days ago

attic

Multi-tenant Nix Binary Cache

Stars1,838

Forks160

Last commit8 days ago

nil

NIx Language server, an incremental analysis assistant for writing in Nix.

Stars1,830

Forks66

Last commit4 months 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 project Star on GitHub