Docker Sandboxes

“Just use docker sandbox or iron proxy to replicate network control/cred swapping”

“sandboxes the agent in a micro vm running on the host and locks down access”

“The default file access is just the directory you create the sandbox under.”

“the "you need a docker login" makes is pretty much no-go for my use case”

“Docker sandboxes seem to be a good solution that also employs virtualization.”

“Concept is great - works quite well - I often have multiple short lived sandboxes running at once.”

“CLI works on Fedora. Been using it daily for ~ a week.”

“my team works on mcp integration with sbx. A solution I've been trying is this”

“But sbx is a bit annoying to use with OpenCode for instance”

“For my workload, it doesn't feel any slower than running it directly on the host.”

“I’ve been using this pretty extensively for a few months on Mac and Linux and have been super happy with it.”

“You only mount the project dir so you can only loose your current changes”

“Finally, a way to run --dangerously-skip-permissions without having a mild heart attack every time the agent decides to rm -rf a mystery directory.”

“An enforced required login is a net negative value - it means rug pulls in the future.”

“the disk space usage was growing significantly, I need to login multiple times for each sandbox, it's closed source”

“this one does that with less config, also with this agents can run docker”

“Like others here I'm also saddened by the login requirement”

“When I previously looked it did not (the reason being that they were already using VMs on Windows/macOS but not on Linux).”

“Docker is not a security boundary. It never has been meant to be”

“a batteries included alternative to firecracker with a couple of new ideas tossed into the mix”

“it works great out of the box with two key features”

“There is no reason to require a login for creating local mini sandboxes.”

“I hope one day Linux will be able to support the exclusive MacOs/Windows technology of Docker Sandboxes.”

“Tomorrow they're gonna add limits on sandbox runs without a premium account too”

“Though, they need to remove the login requirement.”

“I am sad that they are asking for a login here though, which doesn't make any sense to me.”

“gives you a meaningfully more secure environment to run it in”

“It's been a bit of a pain to figure out and maintain the set of tools I provision into the sandbox”

“Docker Sandbox is in the right direction. But there's a lot of parts that are still not ironed out yet.”

“Locks things way down so that the agent only has access to the files you give it”

“Better isolation than running it in a container.”

“it's not available for Linux (so no AWS, no GCP, etc.)”

“Docker sandboxing is kinda nice, but not enough to trust an LLM even with my messaging accounts.”

“switched to Docker sandboxes since they switched to mircoVMs too”

“I'd say that they are on a good path. However in the end I'd expect it to be a standalone application and ecosystem, not tied to docker/moby”

“I believe this is likely the only downside, but for good reasons!”

“We've seen a lot of developers immediately reach for Docker as a quick way to fence agents in.”

“It'll let you use Claude Code + Containers without Docker-in-Docker.”

“uses MicroVM isolation to solve this exact problem”

“Exactly for this problem, the docker sandbox command was added to the cli”