-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SEGV when pushing layer from Google Cloud Build -> Artifact Registry #1604
Comments
Note: I changed to use |
This problem is still happening. I get the above stack trace when I run with BUT, it works when I use |
Naive guess at the problem My guess is that the problem is w/ the https://github.com/GoogleCloudPlatform/docker-credential-gcr/ library. The stack trace above seems to indicate this. And the BROKEN Lines 29 to 36 in 7b64954
WORKS (the kaniko/deploy/Dockerfile_debug Lines 32 to 34 in 7b64954
|
tl;dr if kaniko wants to build this static binary, they need to pass more flags: golang/go#24787 (comment) |
This change likely fixes #6327. As of today, Kaniko `v1.6.0` is the newest released version. Using that version directly results in the crash described in GoogleContainerTools/kaniko#1604. However, using the `v1.6.0-debug` image works, I _think_ because of a different version of the `docker-credentials-gcr` helper as I described in GoogleContainerTools/kaniko#1604 (comment) Updating Kaniko may also help #6336
I have same issue and v1.6.0-debug helps me |
Actual behavior
The above error happens when after Kaniko builds a docker layer and tries to push it from Cloud Build to artifact registry.
cloudbuild.yaml
The Dockerfile I'm building is here: https://github.com/googleapis/google-cloud-cpp/compare/master...devjgm:cloud-build?expand=1#diff-c1691ed788ae6246565bad5ac37a26da8a3ee735f4c2e8f07b5b205ad47b4f26
The artifact registry repo exists:
Expected behavior
I believe I correctly followed the instructions at https://cloud.google.com/build/docs/kaniko-cache and I expected Kaniko to successfully upload the layers and final image to artifact registry, but instead it crashes.
To Reproduce
If this is not a known bug that I'm hitting, I can try to distill the repro steps to something smaller.
Additional Information
Please provide or clearly describe any files needed to build the Dockerfile (ADD/COPY commands)
Triage Notes for the Maintainers
--cache
flagThe text was updated successfully, but these errors were encountered: