alt Hacker NewsIf you haven’t already been running your agents in containers, you’re crazy. That said, this looks like a great way to manage those containers.
Replies
Well, a lot of people haven't been running NodeJS libraries in containers for ages, which seems even more risky.
But then it decides to exfiltrate all your shit even inside the container. Which is something I'm trying to lock down at work atm.
Everything needs to go through a proxy, whitelisted domains only, plus credential swapping/re-signing so that the agent never has the real credentials. Docker sandbox looks quite good (September) but I've been using iron proxy (if the author is reading this, fucking thank you bro!) to great effect.
I still haven't cracked "what if the agent decides to drop parts of your codebase somewhere it shouldn't" yet, but I'll figure it out.
I have been running my dev setup in orb machines before agents. Very convenient when you have 50 Python or nodes deps.
many common local containers are not that hard for modern models to escape...
As an example I run opencode and anything related agent-related in its own dedicated KVM VM with its own LVM logical volumes for storage on a headless server. This has no access whatsoever to the personal data that lives on my laptop and workstation desktop PC. The VM gets periodically imaged and backed up, and is relatively easy to move between host machines if I need to.
One benefit of doing this is that I can leave it doing long term slow things with slow but capable LLMs on a truly 24x7 basis without worrying about it being interrupted by a laptop being closed/going to sleep, or workstation level software updates/reboots on my primary desktop PC.
You're running them in containers, and not in VMs on separate network through network filter and logger?