-
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
error building image: error building stage: failed to get filesystem from image: stream error: stream ID 3; PROTOCOL_ERROR #1360
Comments
also see this error from time to time, using jenkins + kubernetes plugin |
Same problem running Jenkins + K8s plugin. ref: |
Same problem running tekton... |
Any idea for this? |
try to reset GOPROXY
|
same error |
1 similar comment
same error |
Seems like docker hub pull frequency issue,when I change the registry to private, this problem not show again!! |
Can anyone in the thread here confirm:
Trying to understand if this issue is still relevant, if this is a kaniko issue, and how to address the friction here - possibly a fix (depending on root cause), a better error message (if possible) or some documentation |
I'm seeing a similar (but technically slightly different) error on Running via Jenkins agents on EKS using ECR pull-through cache for dockerhub. I have a daily pipeline that builds in four images (read: four upstream dockerhub image dependencies) for our build process - so very low number of source images, and the pipelines have been operating properly for months. All jobs run in parallel, but in isolation -- they each get their own Jenkins agent (but they all route to the internet in the same way). I added a fifth parallel job of the same shape and suddenly saw this error. Replaying the pipeline resulted in inconsistent behavior -- different jobs fail, but with the same error. Given the low number of pulls, it didn't appear to be a pull limit issue, but I swapped out the source images anyway for troubleshooting -- instead of relying on the ECR pull-through, I pointed our source images to ECR-public (e.g. golang and debian upstream). After this change the pipelines appear to have stabilized -- where I could consistently get at least one job to fail before, the jobs now appear to operate as expected. Hope this helps. Thanks to the maintainers for this great tool! |
Actual behavior
kaniko breaks from time to time with this error:
error building image: error building stage: failed to get filesystem from image: stream error: stream ID 3; PROTOCOL_ERROR
I don't have find a way to systematically reproduice it.
Context : I use kaniko with GitLab CI (GitLab Runner).
Expected behavior
Log when it's working:
Log when it's not working:
To Reproduce
Additional Information
kaniko version : i use the docker image gcr.io/kaniko-project/executor:debug
GitLab Runner version 13.1.1
Runner host inside kubernetes 1.17.7 in Azure Kubernetes Service.
Triage Notes for the Maintainers
--cache
flagThe text was updated successfully, but these errors were encountered: