How to add a desk template during self-deployment?

[LoverJoker]

Thanks for open-sourcing this awesome project.

When using self-deployment, I tried to build a template with the file below but it always failed. I then switched to the official e2b.dev environment to try and it also failed. After checking the source code, I found that this API returned an error:

• e2b.Dockerfile

# You can use most Debian-based base images
FROM  e2bdev/desktop:latest

• Error

{
  data: {
    buildID: 'dd5e1807-2ca3-498c-8195-a3d6ca621e51',
    logs: [],
    status: 'error',
    templateID: 'msm0f7gzzihk5imiyej5'
  },
  response: Response {
    status: 200,
    statusText: 'OK',
    headers: Headers {
      'content-type': 'application/json; charset=utf-8',
      date: 'Fri, 06 Jun 2025 08:00:03 GMT',
      'content-length': '113',
      via: '1.1 google',
      'alt-svc': 'h3=":443"; ma=2592000,h3-29=":443"; ma=2592000'
    },
    body: ReadableStream { locked: true, state: 'closed', supportsBYOB: true },
    bodyUsed: true,
    ok: true,
    redirected: false,
    type: 'basic',
    url: 'https://api.e2b.app/templates/msm0f7gzzihk5imiyej5/builds/dd5e1807-2ca3-498c-8195-a3d6ca621e51/status?logsOffset=120'
  }
}

Why did this happen?
Also, how do I publish a public template?

[linear]

E2B-2456 How to add a desk template during self-deployment?

[jakubno]

Hey @LoverJoker, what version of CLI do you use? It looks like it could be caused by a bug, which was in version 1.4.2. It was fixed in 1.4.3.

You can make the template public via `e2b template publish.

Could you share your use case with me, if you don't mind? I'm curious about why someone would choose to self-host and still need to publish templates.

[LoverJoker]

Hey, @jakubno
I pulled the latest https://github.com/e2b-dev/E2B code, confirmed CLI package.json version is 1.4.3. After building locally with npm build, I ran node ./dist/index.js template build -c "/root/.jupyter/start-up.sh" but encountered the same error. I then upgraded the global e2b (official) to 1.4.3 – the error persists. Am I missing steps?

Note: I self-deploy for learning purposes, as many influential projects use E2B. Thanks for building such great software.

[jakubno]

It looks like you are encountering this error:

/root/.jupyter/start-up.sh: No such file or directory\n",
    "[2025-06-06T07:59:53Z] [cmd] [exit 127]: exit status 127\n",
    "[2025-06-06T07:59:53Z] ...\n",
    "[2025-06-06T07:59:53Z] Postprocessing failed: error running command: command failed: exit status 127\n"

The exit code 127 means an "Out of memory" error. It seems the template needs more memory than the default 1024 MiB. To avoid these problems, we currently use 8 GiB for the desktop template. Can you try increasing the memory? It's --memory-mb flag, you can find more in here

[LoverJoker]

That doesn't seem to be the issue. I just tried building with template build --memory-mb 8192 --cpu-count 8 -c "/root/.jupyter/start-up.sh" – the same error persists. I confirmed the memory parameter took effect because when I tried 8193, it enforced even-number requirement.

• logs

{
  data: {
    buildID: '9b7b0b6f-6f83-478f-bc78-d84b57139a9e',
    logs: [],
    status: 'error',
    templateID: '5fwylbe4i56s8al8fc1f'
  },
  response: Response {
    status: 200,
    statusText: 'OK',
    headers: Headers {
      'content-type': 'application/json; charset=utf-8',
      date: 'Fri, 06 Jun 2025 12:30:52 GMT',
      'content-length': '113',
      via: '1.1 google',
      'alt-svc': 'h3=":443"; ma=2592000,h3-29=":443"; ma=2592000'
    },
    body: ReadableStream { locked: true, state: 'closed', supportsBYOB: true },
    bodyUsed: true,
    ok: true,
    redirected: false,
    type: 'basic',
    url: 'https://api.e2b.app/templates/5fwylbe4i56s8al8fc1f/builds/9b7b0b6f-6f83-478f-bc78-d84b57139a9e/status?logsOffset=119'
  }
} 
Error: 
❌ Building sandbox template 5fwylbe4i56s8al8fc1f failed.
Check the logs above for more details or contact us (https://e2b.dev/docs/getting-help) to get help.

    at ame (/Users/jokerliang/work/mc2/e2b/E2B/packages/cli/dist/index.js:169:79)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async e.<anonymous> (/Users/jokerliang/work/mc2/e2b/E2B/packages/cli/dist/index.js:153:203)

[Mashiro2000]

I'm having the same issue. Deployed the latest version.

[dobrac]

Hi @LoverJoker, I see you're specifying the start command -c "/root/.jupyter/start-up.sh", but that is not valid for the Desktop template. The error 127 you're seeing mean's the start-up.sh file doesn't exist.

@Mashiro2000 is this the same issue for you too?

[Mashiro2000]

Hi @LoverJoker, I see you're specifying the start command -c "/root/.jupyter/start-up.sh", but that is not valid for the Desktop template. The error 127 you're seeing mean's the start-up.sh file doesn't exist.

@Mashiro2000 is this the same issue for you too?

My problem is caused by #731

[LoverJoker]

I removed the -c command but it still didn't work. However, I manually built the image using the Dockerfile from the local desktop project, and it succeeded. Does this mean there's an issue with the e2bdev/desktop:latest image on DockerHub?

[jakubno]

I've just tried with e2bdev/desktop:latest, and I was able to build it successfully. Can you share what error you are getting? Also, is this on your self-deployed infrastructure or also running against our production?