GoogleContainerTools / kaniko

Build Container Images In Kubernetes
Apache License 2.0
14.88k stars 1.44k forks source link

Failed to push the docker image to private registry in the first run, but works with second run #1365

Open Sharathmk99 opened 4 years ago

Sharathmk99 commented 4 years ago

Actual behavior Failed to push the docker image to private registry. If i re-run the same pod again, it works.

Expected behavior Able to push the docker image to private registry

To Reproduce Steps to reproduce the behavior:

  1. Create Deployment in Kubernetes cluster

Additional Information Error message,

error pushing image: failed to push to destination xxxx/xxxxxxxx:latest: POST https://xxxxx/v2/xxxxxx/blobs/uploads/?from=xxxxxx&mount=sha256%3A9b8d369425a7a146f144537f9124c7ba4b97f1c4c5796f4fabc571a4f055a042: UNKNOWN: unknown error; map[Err:map[] Op:Post URL:http://backend:5000/v2/xxxxxx/blobs/uploads/?from=xxxxxx&mount=sha256%3A9b8d369425a7a146f144537f9124c7ba4b97f1c4c5796f4fabc571a4f055a042] Triage Notes for the Maintainers

Description Yes/No
Please check if this a new feature you are proposing
  • - [ ]
Please check if the build works in docker but not in kaniko
  • - [ ]
Please check if this error is seen when you use --cache flag
  • - [ ]
Please check if your dockerfile is a multistage dockerfile
  • - [ ]
tejal29 commented 4 years ago

@Sharathmk99 Can you please share more container logs.