Secure and with docker.socket access!

[jdaln]

Hello,

I came by while searching for something exactly like your repo.

The first things I was happy about is to read this:

LibreCodeInterpreter/README.md

Line 7 in eb42153

A secure, open-source code interpreter API that provides sandboxed code execution in isolated Docker containers. Compatible with LibreChat's Code Interpreter API.

Then, I searched "docker.socket" and saw this:

LibreCodeInterpreter/docker-compose.yml

Line 37 in eb42153

- /var/run/docker.sock:/var/run/docker.sock

I have to admit that this is confusing.

[usnavy13]

Thanks for raising this — it's a fair observation.

The Docker socket is mounted into the API container (the control plane), not into the execution containers where untrusted code runs. The API needs Docker socket access because it uses the Docker SDK to create, manage, and destroy the sandboxed execution containers on the fly.

The security hardening (no network, read-only filesystem, all capabilities dropped, noexec tmpfs, no-new-privileges, resource limits) is applied to the execution containers — the ones that actually run user-submitted code. Those containers never have access to the Docker socket.

So the trust boundary is: the API is a trusted component that orchestrates isolated containers, similar to how Kubernetes or other container orchestration tools need privileged access to manage unprivileged workloads.

[jdaln]

Thank you for checking this! That was also my understanding but the API is perhaps over-trusted since it is an exposed service.
Perhaps a solution like this would be safer? https://github.com/Tecnativa/docker-socket-proxy

[usnavy13]

Thank you for checking this! That was also my understanding but the API is perhaps over-trusted since it is an exposed service. Perhaps a solution like this would be safer? https://github.com/Tecnativa/docker-socket-proxy

Im moving towards a single unified image that uses nsjail for execution to simplify the deployment stack. Hopefully ill merge this in the next few days. It has the added benefit of addressing the docker socket issues https://github.com/usnavy13/LibreCodeInterpreter/tree/nsjail