I missed the one directory part, I'd definitely recommend making that more flexible. With my equivalent of this I often mount multiple repositories into a single VM, two examples:
- a bunch of gitops repos: terraform mono repo, argocd-esk conf repo, grafana provisioning repo, etc.
- frontend + backend repo (tbh may merge these to a mono-repo, but here we are)
I think the auto detection is interesting, but tbh with my solution I've been happy with just install all the tools regardless of what a specific project needs - with a COW base layer this is cheap.
Re:Devvm.dev: One VM for every project
by thehamkercat on Friday November 06, 2026 @04:32PM
(#50398809)
fyi, docker sandbox is CLOSED SOURCE, in the year of our lord 2026
Like Docker Sandbox this meets what I think should be our standards in the AI age: kernel isolation and secret shielding in addition to network and disk isolation.
The things that are design choices for these tools are * agent integration * docker image composition * are vms more persistent or throw away * managing configuration
I have been working on a similar project because I haven't seen one before that to me didn't have design deficiencies. This project looks good to me but I need to try it out now and experience the design choices.