Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Docker Sandboxes – Disposable, isolated sandboxes for AI agents

docker.com

Post reply on HN
Print view View original

141–150 of 450 posts

Re: Docker Sandboxes – Disposable, isolated sandboxes for AI agents

#141

Post by vdfs »

Grimburger wrote: post #37

> Each agent runs inside a dedicated microVM with your dev environment What'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

Your example is not complete, you have to show how it will run claude/codex, you have to do extra things to install run and mount folders there, this one does that with less config, also with this agents can run docker, lxd doesn't allow you to do that

Re: Docker Sandboxes – Disposable, isolated sandboxes for AI agents

#143

Post by Izmaki »

TheqO wrote: post #115
Grimburger wrote: post #37

> Each agent runs inside a dedicated microVM with your dev environment What'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

There are many devs that have little to no experience of Linux, like the hundreds of thousands of .Net and Java CRUD devs in enterprise companies using Windows. There is a need for a Docker desktop like GUI for this market.

When I was a teen I had no experience with software development. Then I went to school and learned about it. Now I'm making money doing this thing because I became quite good.

The world didn't fit around me, so I made "me" fit around "the world". I bet those stubborn dinosaurs can learn a new trick or two also, if management lets them do it during working ours...

Re: Docker Sandboxes – Disposable, isolated sandboxes for AI agents

#144

Post by aborsy »

zingar wrote: post #29
notsirius wrote: post #9

been using this for a while - works great! Has also had a lot of updates over the past year so worth checking out again if you tried it a while ago

Do the agents come preinstalled in the images? Or do they somehow use whatever I’ve installed locally? The former makes sense to me but then I’m wondering whether the sandbox images stay up to date with new releases of each image.

The agent is per installed. If there is an update to the agent, the VM notifies you on a first run and updates it if you approve.

Other than the login problem, it’s a decent option.

Re: Docker Sandboxes – Disposable, isolated sandboxes for AI agents

#145

Post by narinciye »

d2p wrote: post #117

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 supporting Linux that I subscribed to have gone unresponded to. OpenShell loo…

It must be a joke that this tool is not supported on linux yet, although docker is built on top of linux containers. Shame on docker.

Re: Docker Sandboxes – Disposable, isolated sandboxes for AI agents

#146

Post by Narushia »

d2p wrote: post #117

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 supporting Linux that I subscribed to have gone unresponded to. OpenShell loo…

I was able to install it on Fedora from the .rpm distributed on their GitHub releases: https://github.com/docker/sbx-releases/releases

Re: Docker Sandboxes – Disposable, isolated sandboxes for AI agents

#147

Post by nzjrs »

rusch wrote: post #58

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 in. Closest open source I have seen is https://earendil-works.github.io/gondol…

If you just need a python+venv sandbox with dev-first UX, no container build step needed, and no startup cost then I am using https://github.com/nzjrs/sandbubble in prod.

Re: Docker Sandboxes – Disposable, isolated sandboxes for AI agents

#148

Post by LeBit »

speedgoose wrote: post #123
dethos wrote: post #99

The other day I saw this: https://nono.sh/ Haven't tested it yet, but it seems to address the same issue as Docker Sandboxes, but in a different way.

I have tested it and the big advantage is that is has access to the local development tools. But it’s not as well sandboxed for sure.

Why do you say that?

Eg, if used with Colima in macOS, it means I can run a devcontainer in an isolated VM and Nono inside the devcontainer can restrict a lot what can and cannot be done.

You get credentials proxying and network outbound limits.

How is Docker Sandbox better sandboxed?

Re: Docker Sandboxes – Disposable, isolated sandboxes for AI agents

#149

Post by LeBit »

weinzierl wrote: post #132
TheRoque wrote: post #121

Earlier quoted context omitted.

Wouldn't it need a super critical exploit, I mean zero-day vulnerability, to escape from that kind of sandbox ? And if you think further, then isn't that risk also applicable to pretty much any kind of sandboxing ?

Container escapes are more common than you think. Common enough for AWS not to rely on containers for their serverless functions, common enough for Google to say: "Untrusted code shouldn't rely on the container security boundary [..]" [1] The same is not applicable for any kind of sandboxing for two reasons: 1. The boundary is in the kernal’s own code, enforced by the thing you are trying to be protected from. -> Use…

What if you use tools like bubblewrap or nono inside the container?

Say I want to use pi inside a container. If I wrap pi within a bubblewrap or within nono, how is that less secure than using a vm?

Also, I think most people run containers inside VMs anyway and not directly on their hosts (on Mac and windows you have to use a vm anyway).

Re: Docker Sandboxes – Disposable, isolated sandboxes for AI agents

#150

Post by mellowagain »

rusch wrote: post #58

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 in. Closest open source I have seen is https://earendil-works.github.io/gondol…

ive been using https://github.com/Gerharddc/litterbox
Post reply on HN