-
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
Manifest with digest 'sha256:884ac2144c3ee154bd67271e99bc6ef00f430092750167729b0321ab55fde5ec' has media type 'application/vnd.docker.distribution.manifest.list.v2+json', but client accepts 'application/vnd.docker.distribution.manifest.v2+json'." #1465
Comments
Experiencing the same issue on all App Engine Flexible Environment. The App Engine standard environment deployments succeed. |
Same issue. App Engine Flex Environment. I tried go1.13 but it did not help. |
Same issue here. Go1.13 didn't help. Any other tips to try to solve the issue? |
Same issue. Nothing appears to be working and our dev team has grinded to a halt this week. It's bad |
I can confirm this solution from a Google engineer worked (at least for me). Downgrade gcloud to the previous version
|
Re @albeebe's comment: The fix required us to roll back our GAE Flex Go builder images and for you to downgrade your cloudsdk version. We are investigating the root cause, which may (or may not) lie in Kaniko. |
We are still working on our root cause analysis, but the initial results indicate it could be an incompatibility with a recent change to use manifest lists for the |
Thanks @sbuss. Kaniko will try to add support manifest list soon! |
@sbuss @tejal29 does this reproduce at HEAD? I'm just speculating, but I'm fairly confident this was fixed almost two years ago. The executor image is very old:
I believe the relevant changes to go-containerregistry were merged into kaniko in #680 |
Thanks @jonjohnsonjr. I looked in the code and on master i think the v1.3.0 should fix it. |
Is this fixed? |
Currently, I'm stuck on this issue. The build doesn't go further. Do we know a work around? |
Are you using the latest kaniko release? It sounds like this may have been fixed a while ago. |
Actual behavior
A clear and concise description of what the bug is.
Tried to deploy on AppEngine Flexible code I already deployed before.
Error:
Expected behavior
A clear and concise description of what you expected to happen.
Expected to build.
To Reproduce
Steps to reproduce the behavior:
Additional Information
Please provide either the Dockerfile you're trying to build or one that can reproduce this error.
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: