logoalt Hacker News

gregwebs • yesterday at 6:56 PM • 2 replies • view on HN

This looks quite similar to docker sandbox (sbx). It uses Lima for VMs under the hood. Windows advertised as not supported (Lima is missing features on Windows).

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.

I have been working on a similar project because I haven't seen one before that to me didn't have security design deficiencies. This project looks to have made good design decisions around security.

The things that are design choices for these tools are

  * agent integration
  * docker image composition
  * are vms more persistent or throw away
  * managing configuration
It does look like it has some design decisions that are optimal for convenience but might lead to inflexibility. It assumes 1 VM per directory. It is trying to auto-detect what someone needs in an image and provide well integrated images and tools out of the box but I don't see how to just provide my own image.

Replies

thehamkercat • yesterday at 9:32 PM

fyi, docker sandbox is CLOSED SOURCE, in the year of our lord 2026

https://github.com/docker/sbx-releases

mnahkies • yesterday at 7:35 PM

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.