kaniko icon indicating copy to clipboard operation
kaniko copied to clipboard

Published 20 hours ago • verified publisher icon GoogleContainerTools

Fail pushing image to Nexus with v1.9.2-debug, ok with v1.9.1-debug

Open mguillem opened this issue 1 year ago • 6 comments

Actual behavior

With v1.9.2-debug pushing a (quite large) image to Nexus fails with following message:

09:57:26.594  error pushing image: failed to push to destination svr-nexus01.#masked#:8128/#masked#: PATCH https://svr-nexus01.#masked#:8128/v2/#masked#/blobs/uploads/e92e4712-9a8b-4624-9bf2-22bb84d72065: UNKNOWN: unknown

Additional Information

  • exactly the same build works fine with v1.9.1-debug.
  • v1.9.2-debug works fine for other images we are building & pushing

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
  • - [ ]

mguillem avatar Apr 05 '23 10:04 mguillem

Same issue on pushing to gitlab registry: error pushing image: failed to push to destination [dest]: Patch "[...]: use of closed network connection. Reverting back to v1.9.1-debug also solved the issue in this case

EivanRazgriz avatar Apr 12 '23 09:04 EivanRazgriz

Same situation for me, pushing a large image to DigitalOcean via GitLab CI/CD:

error pushing image: failed to push to destination registry.digitalocean.com/[dest]: Post "[...]: GET [...]: unexpected status code 400 Bad Request". Reverted back to v1.9.1-debug and it pushed successfully.

On v1.9.2, it would successfully push a small image to the same registry, but failed on a larger image. v1.9.1 pushes both successfully.

Edit: clarification.

Silentstrike46 avatar Apr 13 '23 15:04 Silentstrike46

same issue when pushing image to private repository.

error pushing image: failed to push to destination rg.fr-par.scw.cloud/xxxxx: Post "https://rg.fr-par.scw.cloud/v2/xxxxx/blobs/uploads/?from=library%2Fubuntu&mount=sha256%3Axxxxx&origin=index.docker.io": GET https://api.scaleway.com/registry-internal/v1/regions/fr-par/tokens?scope=repository%3Afxxxxx%3Apull%2Cpush+repository%3Alibrary%2Fubuntu%3Apull&scope=repository%3Axxxxx%3Apush%2Cpull&service=registry: unexpected status code 400 Bad Request: {"message":"Invalid Argument for permission"}

fix by using v1.9.1-debug.

ywang-psee avatar Apr 19 '23 11:04 ywang-psee

Hi Team, Is this issue fixed in the latest version ?

rajathar avatar Oct 10 '23 15:10 rajathar

I have seen the same symptoms on v1.19.2-debug while v1.9.1-debug works.

sopelt avatar Jan 17 '24 13:01 sopelt

I have seen these symptoms on v1.16.0, too. Most Dockerfiles worked, but some not.

INFO[0325] Pushing image to repository.XXX:8445/XXX/tauchausguss-temperaturen:213ef1ba78ed8aafac773e8b202d6b3b108ee015 
error pushing image: failed to push to destination repository.XXX:8445/XXX/project-name:213ef1ba78ed8aafac773e8b202d6b3b108ee015: PATCH https://repository.hkm.de:8445/v2/XXX/project-name/blobs/uploads/2a79c191-68a6-4881-9f64-e59063fe8db7: UNKNOWN: unknown

Upgrading to v1.22.0 fixed it.

michaelkebe avatar Apr 09 '24 08:04 michaelkebe