Skip to main content

Documentation Index

Fetch the complete documentation index at: https://e2b.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

When the CLI pushes a Docker image to the build registry, you may hit an authentication error because Docker doesn’t send any credentials to the registry. The fix is to mark E2B’s local registry proxy as an insecure registry so Docker routes through it.

​
macOS

  1. Open Docker Desktop.
  2. Go to Settings.
  3. Go to Docker Engine.
  4. Add the following line to the JSON configuration:
{
  "insecure-registries": ["host.docker.internal:49984"]
}
A full configuration may look like this: 
{
  "builder": {
    "gc": {
      "defaultKeepStorage": "20GB",
      "enabled": true
    }
  },
  "features": {
    "buildkit": true
  },
  "insecure-registries": [
    "host.docker.internal:49984"
  ]
}
This allows Docker to send requests to the local proxy, which handles the authentication.
  1. Click Apply & Restart.

​
Linux

  1. Edit the Docker configuration file (usually /etc/docker/daemon.json). Create it if it doesn’t exist, and add:
{
  "insecure-registries": ["localhost:49984"]
}
  1. Restart Docker:
sudo systemctl restart docker

​
Windows

  1. Open Docker Desktop.
  2. Go to Settings.
  3. Go to Docker Engine.
  4. Add the following line to the JSON configuration:
{
  "insecure-registries": ["host.docker.internal:49984"]
}
  1. Click Apply & Restart.