61–65 of 65 posts
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...
Earlier quoted context omitted.
This has been my experience. I don't use VSCode and every time I've attempted to play with devcontainers I've just given up and gone back to a docker compose file. I love that they tried to extract the feature out into a stand alone thing, but the juice doesn't seem to be worth the squeeze yet.
Devcontainers work nicely with docker compose. It's the only way I use it... Really nice to have it all run containers. https://code.visualstudio.com/docs/devcontainers/create-dev-...
Earlier quoted context omitted.
I am not affiliated with Microsoft and I anal but I think dev box is fine. What we want to avoid is the term dev containers. https://containers.dev/
> I anal There has to be a better way to phrase this
FYI there's a well-starred, corporate-backed, similar functionality, Nix-based product with the same name: https://github.com/jetify-com/devbox https://www.jetify.com/devbox
FYI there's a well-starred, corporate-backed, similar functionality, Nix-based product with the same name: https://github.com/jetify-com/devbox https://www.jetify.com/devbox