e2b-dev · mintlify · Oct 31, 2025 · Oct 31, 2025 · Oct 31, 2025 · Oct 31, 2025
diff --git a/docs/sandbox-template.mdx b/docs/sandbox-template.mdx
@@ -1,142 +1,143 @@
----
-title: "Sandbox templates"
-sidebarTitle: Sandbox customization
----
-
-import LegacyWarningBuildSystem from "/snippets/LegacyWarningBuildSystem.mdx";
-
-<LegacyWarningBuildSystem/>
-
-Sandbox templates allow you to customize the sandbox environment to your needs.
-
-To create a sandbox template, you specify the `e2b.Dockerfile`. We then take this Dockerfile and create a new sandbox template from it and give you back a template ID.
-
-You can then use this template ID to create a new sandbox with the SDK based on the template you created.
-
-## How to create custom sandbox
-
-**Steps**
-1. [Install E2B CLI](#1-install-e2b-cli)
-1. [Initialize sandbox template](#2-initialize-sandbox-template)
-1. [Customize `e2b.Dockerfile`](#3-customize-e2b-dockerfile)
-1. [Build your sandbox template](#4-build-your-sandbox-template)
-1. [Start your custom sandbox](#5-start-your-custom-sandbox)
-
-
-### 1. Install E2B CLI
-
-**Using Homebrew (on macOS)**
-
-<CodeGroup>
-  ```bash Homebrew
-  brew install e2b
-  ```
-</CodeGroup>
-
-**Using NPM**
-
-<CodeGroup>
-  ```bash NPM
-  npm i -g @e2b/cli
-  ```
-</CodeGroup>
-
-### 2. Initialize sandbox template
-The following command will create a basic `e2b.Dockerfile` in the current directory.
-
-<CodeGroup>
-  ```bash bash
-  e2b template init
-  ```
-</CodeGroup>
-
-### 3. Customize `e2b.Dockerfile`
-Now you can customize your sandbox template by editing the `e2b.Dockerfile` file.
-<CodeGroup title="e2b.Dockerfile">
-  ```bash e2b.Dockerfile highlight={2,5}
-  # Make sure to use this base image
-  FROM e2bdev/code-interpreter:latest
-
-  # Install some Python packages
-  RUN pip install cowsay
-  ```
-</CodeGroup>
-
-<Note>
-  Only [Debian-based](https://en.wikipedia.org/wiki/List_of_Linux_distributions#Debian-based) images
-  (e.g., Debian, Ubuntu, or [E2B images](https://hub.docker.com/u/e2bdev)) are supported.
-</Note>
-
-### 4. Build your sandbox template
-Now you can build your sandbox template. We'll use Docker and the E2B CLI.
-What is going to happen is that E2B CLI will call Docker to build the image and then push it to the E2B cloud.
-Then we convert the Docker image to a micro VM that can be then launched as a sandbox with our SDK.
-
-<CodeGroup>
-  ```bash bash
-  e2b template build -c "/root/.jupyter/start-up.sh"
-  ```
-</CodeGroup>
-
-This process will take a moment. In the end, you'll see your template ID that you'll need to use to create a sandbox with the SDK.
-
-### 5. Start your custom sandbox
-Now you can use the template ID to create a sandbox with the SDK.
-
-<CodeGroup>
-  ```javascript JavaScript & TypeScript highlight={4,6}
-  import { Sandbox } from '@e2b/code-interpreter'
-
-  // Your template ID from the previous step
-  const templateID = 'id-of-your-template'
-  // Pass the template ID to the `Sandbox.create` method
-  const sandbox = await Sandbox.create(templateID)
-
-  // The template installed cowsay, so we can use it
-  const execution = await sandbox.runCode(`
-  import cowsay
-  cowsay.say('Hello from E2B!')
-  `)
-
-  console.log(execution.stdout)
-  ```
-  ```python Python highlight={4,6}
-  from e2b_code_interpreter import Sandbox
-
-  # Your template ID from the previous step
-  template_id = 'id-of-your-template'
-  # Pass the template ID to the `Sandbox.create` method
-  sandbox = Sandbox.create(template_id)
-
-  # The template installed cowsay, so we can use it
-  execution = sandbox.run_code("""
-  import cowsay
-  cowsay.say('Hello from E2B!')
-  """)
-
-  print(execution.stdout)
-  ```
-</CodeGroup>
-
-## How it works
-Every time you are building a sandbox template, we create a container based on the [`e2b.Dockerfile`](/docs/sandbox-template#3-customize-e2b-dockerfile) file you create in the process.
-We extract the container's filesystem, do provisioning and configuration (e.g. installing required dependencies), and start a sandbox.
-
-Then, these steps happen:
-
-    1. We take the running sandbox.
-    2. (Only if you specified the [start command](/docs/sandbox-template/start-cmd), otherwise this step is skipped) Execute the start command.
-    3. Wait for readiness (by default 20 seconds if start command is specified, otherwise immediately ready). Readiness check can be configured using [ready command](/docs/sandbox-template/ready-cmd).
-    4. Snapshot the sandbox and make it ready for you to spawn it with the SDK.
-
-We call this sandbox snapshot a _sandbox template_.
-
-<Note>
-  **Sandbox Snapshot**
-
-  Snapshots are saved running sandboxes. We serialize and save the whole sandbox's filesystem together with all the
-  running processes in a way that can be loaded later.
-
-  This allows us to load the sandbox in a few hundred milliseconds any time later with all the processes already running
-  and the filesystem exactly as it was.
-</Note>
+---
+title: "Sandbox templates"
+sidebarTitle: Sandbox customization
+noindex: true
+---
+
+import LegacyWarningBuildSystem from "/snippets/LegacyWarningBuildSystem.mdx";
+
+<LegacyWarningBuildSystem/>
+
+Sandbox templates allow you to customize the sandbox environment to your needs.
+
+To create a sandbox template, you specify the `e2b.Dockerfile`. We then take this Dockerfile and create a new sandbox template from it and give you back a template ID.
+
+You can then use this template ID to create a new sandbox with the SDK based on the template you created.
+
+## How to create custom sandbox
+
+**Steps**
+1. [Install E2B CLI](#1-install-e2b-cli)
+1. [Initialize sandbox template](#2-initialize-sandbox-template)
+1. [Customize `e2b.Dockerfile`](#3-customize-e2b-dockerfile)
+1. [Build your sandbox template](#4-build-your-sandbox-template)
+1. [Start your custom sandbox](#5-start-your-custom-sandbox)
+
+
+### 1. Install E2B CLI
+
+**Using Homebrew (on macOS)**
+
+<CodeGroup>
+  ```bash Homebrew
+  brew install e2b
+  ```
+</CodeGroup>
+
+**Using NPM**
+
+<CodeGroup>
+  ```bash NPM
+  npm i -g @e2b/cli
+  ```
+</CodeGroup>
+
+### 2. Initialize sandbox template
+The following command will create a basic `e2b.Dockerfile` in the current directory.
+
+<CodeGroup>
+  ```bash bash
+  e2b template init
+  ```
+</CodeGroup>
+
+### 3. Customize `e2b.Dockerfile`
+Now you can customize your sandbox template by editing the `e2b.Dockerfile` file.
+<CodeGroup title="e2b.Dockerfile">
+  ```bash e2b.Dockerfile highlight={2,5}
+  # Make sure to use this base image
+  FROM e2bdev/code-interpreter:latest
+
+  # Install some Python packages
+  RUN pip install cowsay
+  ```
+</CodeGroup>
+
+<Note>
+  Only [Debian-based](https://en.wikipedia.org/wiki/List_of_Linux_distributions#Debian-based) images
+  (e.g., Debian, Ubuntu, or [E2B images](https://hub.docker.com/u/e2bdev)) are supported.
+</Note>
+
+### 4. Build your sandbox template
+Now you can build your sandbox template. We'll use Docker and the E2B CLI.
+What is going to happen is that E2B CLI will call Docker to build the image and then push it to the E2B cloud.
+Then we convert the Docker image to a micro VM that can be then launched as a sandbox with our SDK.
+
+<CodeGroup>
+  ```bash bash
+  e2b template build -c "/root/.jupyter/start-up.sh"
+  ```
+</CodeGroup>
+
+This process will take a moment. In the end, you'll see your template ID that you'll need to use to create a sandbox with the SDK.
+
+### 5. Start your custom sandbox
+Now you can use the template ID to create a sandbox with the SDK.
+
+<CodeGroup>
+  ```javascript JavaScript & TypeScript highlight={4,6}
+  import { Sandbox } from '@e2b/code-interpreter'
+
+  // Your template ID from the previous step
+  const templateID = 'id-of-your-template'
+  // Pass the template ID to the `Sandbox.create` method
+  const sandbox = await Sandbox.create(templateID)
+
+  // The template installed cowsay, so we can use it
+  const execution = await sandbox.runCode(`
+  import cowsay
+  cowsay.say('Hello from E2B!')
+  `)
+
+  console.log(execution.stdout)
+  ```
+  ```python Python highlight={4,6}
+  from e2b_code_interpreter import Sandbox
+
+  # Your template ID from the previous step
+  template_id = 'id-of-your-template'
+  # Pass the template ID to the `Sandbox.create` method
+  sandbox = Sandbox.create(template_id)
+
+  # The template installed cowsay, so we can use it
+  execution = sandbox.run_code("""
+  import cowsay
+  cowsay.say('Hello from E2B!')
+  """)
+
+  print(execution.stdout)
+  ```
+</CodeGroup>
+
+## How it works
+Every time you are building a sandbox template, we create a container based on the [`e2b.Dockerfile`](/docs/sandbox-template#3-customize-e2b-dockerfile) file you create in the process.
+We extract the container's filesystem, do provisioning and configuration (e.g. installing required dependencies), and start a sandbox.
+
+Then, these steps happen:
+
+    1. We take the running sandbox.
+    2. (Only if you specified the [start command](/docs/sandbox-template/start-cmd), otherwise this step is skipped) Execute the start command.
+    3. Wait for readiness (by default 20 seconds if start command is specified, otherwise immediately ready). Readiness check can be configured using [ready command](/docs/sandbox-template/ready-cmd).
+    4. Snapshot the sandbox and make it ready for you to spawn it with the SDK.
+
+We call this sandbox snapshot a _sandbox template_.
+
+<Note>
+  **Sandbox Snapshot**
+
+  Snapshots are saved running sandboxes. We serialize and save the whole sandbox's filesystem together with all the
+  running processes in a way that can be loaded later.
+
+  This allows us to load the sandbox in a few hundred milliseconds any time later with all the processes already running
+  and the filesystem exactly as it was.
+</Note>
diff --git a/docs/sandbox-template/customize-cpu-ram.mdx b/docs/sandbox-template/customize-cpu-ram.mdx
@@ -1,22 +1,23 @@
----
-title: "Customize sandbox CPU & RAM"
-sidebarTitle: Customize CPU & RAM
----
-
-import LegacyWarningBuildSystem from "/snippets/LegacyWarningBuildSystem.mdx";
-
-<LegacyWarningBuildSystem/>
-
-You can customize the CPU and RAM of your sandbox template via E2B CLI.
-
-You'll need to create a sandbox [template first](/docs/sandbox-template).
-
-During the build step, you can specify the CPU and RAM of your sandbox template.
-
-The following command will create a sandbox template with 2 CPUs and 2GB of RAM.
-
-<CodeGroup>
-```bash  Terminal
-e2b template build -c "/root/.jupyter/start-up.sh" --cpu-count 2 --memory-mb 2048
-```
-</CodeGroup>
+---
+title: "Customize sandbox CPU & RAM"
+sidebarTitle: Customize CPU & RAM
+noindex: true
+---
+
+import LegacyWarningBuildSystem from "/snippets/LegacyWarningBuildSystem.mdx";
+
+<LegacyWarningBuildSystem/>
+
+You can customize the CPU and RAM of your sandbox template via E2B CLI.
+
+You'll need to create a sandbox [template first](/docs/sandbox-template).
+
+During the build step, you can specify the CPU and RAM of your sandbox template.
+
+The following command will create a sandbox template with 2 CPUs and 2GB of RAM.
+
+<CodeGroup>
+```bash  Terminal
+e2b template build -c "/root/.jupyter/start-up.sh" --cpu-count 2 --memory-mb 2048
+```
+</CodeGroup>