infra
infra copied to clipboard
e2b-dev
Infrastructure powering E2B - Secure Runtime for AI Agents & Apps
Right now the logs from proxies and API are only accessible in Nomad (and that is for a limited time). We can monitor the errors that users get in SDK...
We want to update the default version that is used for newly built templates to this release after checking if everything is compatible.
Firecracker 1.7 was released and we want to update the default version that is used for newly built templates to this release after checking if everything is compatible.
Users can use only the HTTP protocol when communicating with services they started inside the sandbox. This for example prevents users from communicating with a service they started inside their...
Check if headers aren't removed by nginx proxies used for sandbox networking. I was getting the header inside the sandbox, but it wasn't present when requesting from outside.
Currently, the E2B infra can run only on a single client. We're moving to a multi-client support in order to be able to scale the number of running sandboxes.
When a process in sandbox is killed we are propagating the -1 exit code, but we should also add a message so it it clear that the process was killed...
When running any sudo command, there's this line in the output: ``` user@fc1574dff44b:~$ sudo ls > sudo: unable to resolve host fc1574dff44b: Name or service not known ```
 This is probably caused by the go context again.