Docker containers share the host kernel. Namespaces ≠ sandbox.
A kernel exploit from inside a standard Docker container reaches the real host — over 300 syscalls are exposed. gVisor (Google's open-source user-space kernel) cuts that to ~20.
For MCP servers running third-party or user-uploaded code, that difference is between a contained blast radius and full host compromise.
Docker containers share the host kernel. Namespaces ≠ sandbox.
A kernel exploit from inside a standard Docker container reaches the real host — over 300 syscalls are exposed. gVisor (Google's open-source user-space kernel) cuts that to ~20.
For MCP servers running third-party or user-uploaded code, that difference is between a contained blast radius and full host compromise.
AI 에이전트가 코드를 실행할 때: 컨테이너만으론 부족한 이유
AI 에이전트가 코드를 실행할 때 컨테이너만으로는 부족한 이유와 microVM, gVisor, Wasm 등 샌드박스 기술의 실전 선택 기준을 소개합니다.#AIAnToan #Sandboxing #KhoaHocDuLieu #AIQuanLy
Giới hạn hành vi tự chủ của agent AI thông qua sandboxing – bài viết phân tích rủi ro từ truy cập tool không kiểm soát, lộ trình mạng/hệ thống, và các giải pháp như Docker, Firecracker, gVisor. Tìm hiểu cách tối ưu an toàn trong sản phẩm.
#AIUnsafe #AnToanCongNghe #QuanLyAI #Container #MicroVM #GVisor #DevOps #Cybersecurity
https://www.reddit.com/r/programming/comments/1po8ar9/sandboxing_ai_agents_practical_ways_to_limit/
It has been a really long time since I last wrote something here as life happens, things get busier, etc etc. I am now trying to get back into writing things down and here we go! So, imagine a tool or a service that allows you to run some arbitrary code via a shell. Either through a ssh or more commonly, via a web terminal. How does these tools isolate your code from other people’s code and vice versa ? How come you cannot see other people code or processes ?