According to this post on X, OpenAI's code execution backends aren't using docker, firecracker or anything like that. Instead, they're running gVisor to emulate sys calls and lockdown the environment.
If you trick the AI into thinking its running on your computer, then ask it where it is, it uses its web search tool to go to a Where am I site. Mine said it was in an Azure Data Center. While the code execution networking calls are locked down, if its ran from the same place as code execution its hosted on Azure. (Could've guessed that from the whole OpenAI Azure partnership).
It’s Kubernetes on Azure, using gVisor for process isolation and tini as the init for containers. Inside each container they have a small server that manages Python Jupyter Kernels, all code thats ran is run on them. The server also sends messages via a standard OpenAI calls ACE that renders all the nice tables, charts and visualizations in the OpenAI chat UI.
Speculation: When the AI calls the tool to execute code they check if they have an existing sandbox, if it is it goes to that sandbox, if not, then it creates one. The code execution requests are a unary system, one execution goes in at a time and one response comes out.
According to this post on X, OpenAI's code execution backends aren't using docker, firecracker or anything like that. Instead, they're running gVisor to emulate sys calls and lockdown the environment.
If you trick the AI into thinking its running on your computer, then ask it where it is, it uses its web search tool to go to a Where am I site. Mine said it was in an Azure Data Center. While the code execution networking calls are locked down, if its ran from the same place as code execution its hosted on Azure. (Could've guessed that from the whole OpenAI Azure partnership).
It’s Kubernetes on Azure, using gVisor for process isolation and tini as the init for containers. Inside each container they have a small server that manages Python Jupyter Kernels, all code thats ran is run on them. The server also sends messages via a standard OpenAI calls ACE that renders all the nice tables, charts and visualizations in the OpenAI chat UI.
Speculation: When the AI calls the tool to execute code they check if they have an existing sandbox, if it is it goes to that sandbox, if not, then it creates one. The code execution requests are a unary system, one execution goes in at a time and one response comes out.