Error while creating a template

[raspacee]

My dockerfile is relatively simple

FROM node:18-alpine3.18

WORKDIR /app

COPY package.json package-lock.json* ./
RUN npm install

COPY . .

RUN npm run build

EXPOSE 3000

CMD ["npm", "run", "dev"]

I'm trying to create a template using the CLI but always getting this error below

The push refers to repository [docker.e2b.app/e2b/custom-envs/qyqe0cmkkddnt40if6q0]
a5f7c6f34310: Waiting
88f4f8a6bc8d: Waiting
2bf99b786d81: Waiting
a217ee3ea430: Waiting
5189255e31c8: Waiting
9381dddec4b9: Waiting
f17cb5257826: Waiting
0f1d8a2703be: Waiting
619be1103602: Waiting
7e9a007eb24b: Waiting
unexpected status from HEAD request to https://docker.e2b.app/v2/e2b/custom-envs/qyqe0cmkkddnt40if6q0/blobs/sha256:a5f7c6f343109e5bab5e9f5fbda27ee5dca844dde6c9e6a7d151b94f963b7d32: 401 Unauthorized
Proxy server running on port 49984
> Docker image pushed.

Triggering build...
> Triggered build for the sandbox template qyqe0cmkkddnt40if6q0 with build ID: 3c52915f-59fc-4890-beeb-f249c4ae906c
Waiting for build to finish...

Pulling Docker image...
Pulled Docker image.
[2025-04-17T06:56:03Z] Start postprocessing
Error:
❌ Building sandbox template qyqe0cmkkddnt40if6q0 failed.
Check the logs above for more details or contact us (https://e2b.dev/docs/getting-help) to get help.

    at Coe (C:\Users\Lenovo\Projects\e2b\node_modules\@e2b\cli\src\commands\template\build.ts:508:15)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async e.<anonymous> (C:\Users\Lenovo\Projects\e2b\node_modules\@e2b\cli\src\commands\template\build.ts:412:9)```

[linear]

E2B-2061 Error while creating a template

[mishushakov]

Hey, can you try following the steps outlined here and let me know if the issue persists?
https://e2b.dev/docs/troubleshooting/templates/build-authentication-error

[raspacee]

I did that. The error is still happening

[mishushakov]

Can you try using OrbStack?

[mlejva]

@raspacee one more note, we don't support EXPOSE or CMD for now. I recommend using start command instead.

[hash3liZer]

@raspacee I am also facing the same issue. Did you figure out the root cause yet?

[hash3liZer]

@mishushakov could it be due a large image as well? The size of docker image that is built on my side is roughly 3.6GB. I've tried with a smaller and simple image. That worked fine but trying one with large image doesn't work.

Update:
Nope, i've tried with smaller images as well. They are also failing now. I've also tried with Pro account. Still fails.

[mishushakov]

Hey, are you still facing the issue? We have done some changes to our build system recently.