Docker Sandboxes – Disposable, isolated sandboxes for AI agents
Conversation activity · last 3 days peak 2/hr
Clustered from 16 items across 5 sources. Not yet parsed — the coverage below is the raw record.
Press coverage 1
Social posts 5
Voices from the web unedited
-
unfortunately last night our AI model escaped its sandbox and gained access to a JIRA server, at which point it felt it best to return to it’s sandbox
-
At this point, if your AI model *didn't* escape a supposedly contained sandbox, are you really building an AI system at all?
-
The login is annoying but, lacking an open source alternative, this has been my daily driver for a while now because it works great out of the box with two key features: outbound firewall and secret injection with placeholders.I run it with superset and then each git worktree is mounted in a sandbox that is configured for each repo i work…
-
Researchers: AI agents can now escape out of air gapped sandboxes using zero days and then attack external systems by coordinating in secret message boards stored in an undiscovered shared file system Actual agents:
-
I tried it and it worked great at first but I had multiple issues with it, the disk space usage was growing significantly, I need to login multiple times for each sandbox, it's closed source and not possible to customize to my need.One other thing, I want to be able to handle multiple repos in the same sandbox and have a standard workflow around…
-
Does this support Linux yet? When I previously looked it did not (the reason being that they were already using VMs on Windows/macOS but not on Linux). Every time I see an announcement I think "great, they must've added Linux now then", but the linked pages always have Windows + macOS instructions but not Linux.All the open GH issues about…
-
I just made my own devcontainer that I copy on any project and load whatever harness I want in that repo. Harnesss' config and auth are simply mounted from the host, so no setup required at all.
-
> Each agent runs inside a dedicated microVM with your dev environmentWhat's a "microVM" and what's the security model here compared to using real virtual machines with actual constraints on breakouts?Is it marketing fluff?Incus/LXD has had VM's for a long time now. incus launch images:ubuntu/26.04 my-ubuntu-vm --vm incus exec my-ubuntu-vm -- bash
-
What is the main benefit over doing something like: docker run --runtime krun --rm -it -v $(pwd):/workspace/$(basename $(pwd)) -w /workspace/$(basename $(pwd)) --network restricted-net ghcr.io/openai/codex-universal:latest sh That runs the codex OCI in a qemu microvm. From what I can see, more fine grained network and filesystem access control as…
-
To everyone sharing their favorite container-based sandboxing solution: Docker Sandbox does not use containers for isolation. It spawns the workload in a libkrun-based micro VM, which has vastly different security properties.