Show HN: Devbox – Containers for better dev environments (devbox.ar0.eu)
- Configurable via JSON: Define packages, services, and more in a `devbox.json` file. Share it in your repo for reproducible setups—teammates just run `devbox up`.
- Docker-in-Docker by default: Build and run containers inside your env without extra config.
- Host-friendly: Edit code directly on your machine; the container handles the runtime.
- Templates for quick starts: Built-ins for Python, Node.js, Go, web dev, etc.
- Advanced options: Port mapping, env vars, resource limits, and even mounting your dotfiles.
It's FOSS (MIT license), Linux-focused (Debian/Ubuntu, or WSL2 on Windows), and super easy to install: `curl -fsSL https://devbox.ar0.eu/install.sh | bash`.
Check out the launch page and docs at https://devbox.ar0.eu, or the repo at https://github.com/itzCozi/devbox. I'd love some feedback, stars, or contributions to help grow this into a solid community tool!
30 comments
[ 3.7 ms ] story [ 56.8 ms ] threadhttps://github.com/jetify-com/devbox https://www.jetify.com/devbox
- how is your devbox.json file different from a Dockerfile/Containerfile?
- does your project attempt to provide any isolation security-wise?
I've worked on projects where the original dev has used containers for everything. It's super clunky and annoying. I don't want to use a different bash config just for working on that project. I've set my own up for a reason. All it makes me wonder is what are you afraid of? Why do you feel the need to isolate dev projects to this extent?
Does devbox support mobile development - Flutter or ReactNative?
https://devpod.sh/
Container Shell - https://github.com/jrz/container-shell
However, I use https://www.jetify.com/devbox.
Why should we use yours? What does it do better or differently?
Almost all my stuff still runs on simple VMs because I cannot rely on my clients to take on more complex cloud infrastructure and I don't want to be stuck managing all of the things forever, so my life involves building customer VMs from build scripts that are adequately similar to my Vagrant boxes.
I use the VMs a lot for simple tests (e.g. of wordpress plugins and themes) so I have gone to the trouble of setting up Avahi with alias support, adding options for mailhog, different databases, different webserver setups I use for WP or Laravel or node.js, setting up an automated WP install etc.; so there are two or three starting configurations. I even had one for Magento before I realised I could be a lot happier without Magento in my life.
I guess it looks a fair bit like devcontainers now, and I should consider migrating over to that. But it's solid and under my control and that counts for a lot.
Added GPU pass‑through, engine‑agnostic containers (DEVBOX_ENGINE for Podman/rootless), and alternate config filenames to avoid Jetify collisions—while keeping a tiny, CLI‑first flow that works outside VS Code.
https://github.com/itzCozi/devbox/commit/d05c8980db7fb907f31...