Session
YOLO mode, isolated by design. How Docker's sandboxes change what "allow all" means
Agentic AI. The dream. We gave AI agents our terminals. Then our repositories. Then our credentials. And then we clicked "allow all", because nobody has time to approve every npm install.
And the dream became a nightmare.
Let's be honest: YOLO mode is how most of us work now Prove me I am wrong!
The question isn't if your agent will do something unexpected and dangerous. The question is where it will happen, and how quickly.
Well, we can contain agents in containers, don't we? Well, yes, containers are great tool, I love them, I'm a Docker Captain after all. But a container shares the kernel with your machine, and the code inside was written by an agent a few seconds ago. Nobody reviewed it. Not even the agent.
In this session we do something irresponsible on purpose. I'll give an AI agent full autonomy and a very bad idea, and we'll watch it try. Live. Inside Docker Sandboxes: a microVM per agent, its own kernel, its own Docker daemon, and boundaries for files, network and secrets set before the agent even starts.
Will my laptop survive? Join me and find out.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top