RunPod•4d ago

Error when building serverless endpoint

What happened? I tried to build and deploy a Docker image from my GitHub repository, but it failed with these errors: - First, a 401 Unauthorized error when checking some files (blobs). - Then, a BLOB_UNKNOWN error saying it couldn’t find a required file (sha256:6e909acdb...). Question Could someone help me understand and fix this? I suspect it might be related to the container size – are there limits or known issues with large image pushes? What’s the best way to resolve this? Full error

2025-04-01T19:49:43.319Z [ERROR] error: https://registry.runpod.net/v2/project-deploy/runpod-dockerfile/blobs/sha256:8e2cd6c702e4652f243976aadb15c765834a3816bdb33fafb2c8fcd012524d18 responded 401:
2025-04-01T19:49:43.319Z [ERROR] at /app/serverless-registry/push/index.ts:275:11
2025-04-01T19:49:43.320Z [ERROR] 
2025-04-01T19:49:43.321Z [ERROR] 475 |   body: JSON.stringify(manifestObject),
2025-04-01T19:49:43.321Z [ERROR] 476 |   method: "PUT",
2025-04-01T19:49:43.322Z [ERROR] 477 | });
2025-04-01T19:49:43.323Z [ERROR] 478 |
2025-04-01T19:49:43.324Z [ERROR] 479 | if (!responseManifestUpload.ok) {
2025-04-01T19:49:43.324Z [ERROR] 480 |   throw new Error(
2025-04-01T19:49:43.325Z [ERROR] ^
2025-04-01T19:49:43.326Z [ERROR] error: manifest upload https://registry.runpod.net/v2/project-deploy/runpod-dockerfile/manifests/201214869 returned 400: {"errors":[{"code":"BLOB_UNKNOWN","message":"unknown blob sha256:6e909acdb790c5a1989d9cfc795fda5a246ad6664bb27b5c688e2b734b2c5fad","detail":{}}]}
2025-04-01T19:49:43.326Z [ERROR] at /app/serverless-registry/push/index.ts:480:9
2025-04-01T19:49:43.327Z [ERROR] 
2025-04-01T19:49:43.328Z [ERROR] Bun v1.1.32 (Linux x64)
2025-04-01T19:49:43.329Z [ERROR] Image push finished with wrong exit code: Please view the logs to find out what went wrong. Contact support in case you cannot understand.

2025-04-01T19:49:43.319Z [ERROR] error: https://registry.runpod.net/v2/project-deploy/runpod-dockerfile/blobs/sha256:8e2cd6c702e4652f243976aadb15c765834a3816bdb33fafb2c8fcd012524d18 responded 401:
2025-04-01T19:49:43.319Z [ERROR] at /app/serverless-registry/push/index.ts:275:11
2025-04-01T19:49:43.320Z [ERROR] 
2025-04-01T19:49:43.321Z [ERROR] 475 |   body: JSON.stringify(manifestObject),
2025-04-01T19:49:43.321Z [ERROR] 476 |   method: "PUT",
2025-04-01T19:49:43.322Z [ERROR] 477 | });
2025-04-01T19:49:43.323Z [ERROR] 478 |
2025-04-01T19:49:43.324Z [ERROR] 479 | if (!responseManifestUpload.ok) {
2025-04-01T19:49:43.324Z [ERROR] 480 |   throw new Error(
2025-04-01T19:49:43.325Z [ERROR] ^
2025-04-01T19:49:43.326Z [ERROR] error: manifest upload https://registry.runpod.net/v2/project-deploy/runpod-dockerfile/manifests/201214869 returned 400: {"errors":[{"code":"BLOB_UNKNOWN","message":"unknown blob sha256:6e909acdb790c5a1989d9cfc795fda5a246ad6664bb27b5c688e2b734b2c5fad","detail":{}}]}
2025-04-01T19:49:43.326Z [ERROR] at /app/serverless-registry/push/index.ts:480:9
2025-04-01T19:49:43.327Z [ERROR] 
2025-04-01T19:49:43.328Z [ERROR] Bun v1.1.32 (Linux x64)
2025-04-01T19:49:43.329Z [ERROR] Image push finished with wrong exit code: Please view the logs to find out what went wrong. Contact support in case you cannot understand.

9 Replies

Poddy•3d ago

@joaopresotto

Escalated To Zendesk

The thread has been escalated to Zendesk!

Jason•3d ago

please open a ticket here

PRB•3d ago

@joaopresotto how long was the build + push? i have a theory but need to validate it

joaopresottoOP•3d ago

Almost 10 minutes (the build log goes from 09:22:21 to 09:31:30)

PRB•3d ago

Kk. What happens when you retry?

joaopresottoOP•3d ago

The only difference is that it recovers cached files so it takes less time. However the error remains the same:

{"errors":[{"code":"BLOB_UNKNOWN","message":"unknown blob sha256:6e909acdb790c5a1989d9cfc795fda5a246ad6664bb27b5c688e2b734b2c5fad","detail":{}}]}

PRB•3d ago

i would push it again

joaopresottoOP•3d ago

Still no luck. Do you have any suggestions on what to try next?

joaopresottoOP•2d ago

I've made some changes in the Dockerfile of my github repo and this error was fixed, but I've got another error: Specifically, an executionTimeout is exceeded at the "Pushing image to registry" step when building a serverless endpoint.

Gaming

Programming

Error when building serverless endpoint

Did you find this page helpful?