Default environment variables
Knowing if you are inside a sandbox
Sometimes it’s useful to know if the code is running inside a sandbox. Upon creating a sandbox, useful sandbox metadata is set as environment variables for commands:E2B_SANDBOX
is set totrue
for processes to know if they are inside our VM.E2B_SANDBOX_ID
to know the ID of the sandbox.E2B_TEAM_ID
to know the team ID that created the sandbox.E2B_TEMPLATE_ID
to know what template was used for the current sandbox.
These default environment variables are only accessible via the SDK, when using the CLI you can find them in the form of dot files in the
/run/e2b/
dir:Setting environment variables
There are 3 ways to set environment variables in a sandbox:- Global environment variables when creating the sandbox.
- When running code in the sandbox.
- When running commands in the sandbox.
1. Global environment variables
You can set global environment variables when creating a sandbox.2. Setting environment variables when running code
You can set environment variables for specific code execution call in the sandbox.- These environment variables are scoped to the command but are not private in the OS.
- If you had a global environment variable with the same name, it will be overridden only for the command.
3. Setting environment variables when running commands
You can set environment variables for specific command execution in the sandbox.- These environment variables are scoped to the command but are not private in the OS.
- If you had a global environment variable with the same name, it will be overridden only for the command.