Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

GCR content-type errors #879

Closed
mithrandi opened this issue Dec 20, 2017 · 3 comments
Closed

GCR content-type errors #879

mithrandi opened this issue Dec 20, 2017 · 3 comments

Comments

@mithrandi
Copy link
Contributor

mithrandi commented Dec 20, 2017

I'm seeing a lot of errors logged like this:

ts=2017-12-20T19:50:26.214459657Z caller=warming.go:148 component=warmer err="requesting manifests: getting remote manifest: Get https://gcr.io/v2/kubernetes-helm/tiller/manifests/v2.0.0: http: non-successful response (status=404 body=\"{\
\\"errors\\\":[{\\\"code\\\":\\\"MANIFEST_UNKNOWN\\\",\\\"message\\\":\\\"Manifest with tag 'v2.0.0' has media type 'application/vnd.docker.distribution.manifest.v1+prettyjws', but client accepts 'application/vnd.docker.distribution.manifest.v1+json'.\\\"}]}\")"

This is with Flux 1.1.0 as well as master. The images for the controller(s) in question show as "waiting for cache" forever, presumably due to this error.

@squaremo
Copy link
Member

Thanks for posting this issue @mithrandi. We were also seeing these log messages, as reported in #838. It was fixed in #851, which made its way to master pretty recently, and will be in the next release (soon!).

@squaremo
Copy link
Member

(closing as a duplicate of #838, but please do comment here, or file a further issue, if you still have problems that #851 is supposed to fix)

@mithrandi
Copy link
Contributor Author

Aha! It looks like I was running the master revision just before that was merged, upgrading does resolve the issue as expected.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants