Repository navigation
Documentation: allow sandboxed AI agent to run Docker #2
Description
Problem
I added this config entry to run Docker in the sandboxed environment:
# Docker access
EXTRA_RO_BINDS+=( "/var/run/docker.sock" )Proposed solution
Is it something that could be documented in a "Tips & Tricks" section in the README to ease the onboarding?
Activity
sebalix commentedon Aug 31, 2026
@shleder thank you for your advice, you're right it's probably not a good idea to bind this socket.
Currently I need to run Docker, so your idea to use a custom DOCKER_HOST endpoint is what I chosed 👍 (using https://github.com/Tecnativa/docker-socket-proxy + some minor changes to get finer access granularity on Docker API).
This leads to a missing feature in the current project: ability to set custom environment variables, I'll probably open a PR for that.
EDIT: here #3
simcop2387 commentedon Sep 24, 2026
I'm trying docker-in-docker for this and giving that inner docker's socket to the whole thing so that it won't have access to most other things. Probably still a hole or two but a lot less immediately available to cause havok. It does lead to some issues networking wise (since there's multiple nested network namespace).
didvc commentedon Oct 20, 2026
Added a security note about this rather than a tips section, since the thread already settled the substance. The Docker socket is equivalent to root on the host, so binding it removes the sandbox instead of extending it. The note says that, and points at running a filtering proxy and setting DOCKER_HOST, which is what you ended up doing.
78433af