Getting 401 during image push for serverless, when built from gitrepo
I am getting the following error when pushing image for a serverless endpoint that is built from github. the image build works correctly, but crashloops with the following error during push. I do not have a Container Registry Auth setup in runpod, as I am using public images only, and the build itself worked correctly. Do I need any other kind of auth on runpod to be able to push the image that is built from the github repo?
2025-04-06 13:23:27 [INFO] Pushing image to registry. This takes some time - please be patient. 2025-04-06 13:23:57 [ERROR] 272 | }); 2025-04-06 13:23:57 [ERROR] 273 | 2025-04-06 13:23:57 [ERROR] 274 | if (!layerExistsResponse.ok && layerExistsResponse.status !== 404) { 2025-04-06 13:23:57 [ERROR] 275 | throw new Error(${layerExistsURL} responded ${layerExistsResponse.status}: ${await layerExistsResponse.text()}); 2025-04-06 13:23:57 [ERROR] ^ 2025-04-06 13:23:57 [ERROR] error: https://registry.runpod.net/v2/repo-id/image-endpoint-dockerfile/blobs/sha256:2f4727a86c11bb1033fe3620af260f771dad73b69befcf45f2e2f10e86c3fba3 responded 401:
Solution:Jump to solution
I think I figured it out. It seemd to work when I changed the base image to a runpod* image. earlier. I was using a python/slim image assuming that it is a public image on docker. but looks like runpod supports only using a runpod private base image.
1 Reply
Solution
I think I figured it out. It seemd to work when I changed the base image to a runpod* image. earlier. I was using a python/slim image assuming that it is a public image on docker. but looks like runpod supports only using a runpod private base image.