Problems pulling docker image about kured

[RobCannon]

Can the kured*.yaml file get update to reference the new image location?

[Data-Jack]

Hi all, I can see that this has been fixed in the master now https://github.com/weaveworks/kured/blob/master/kured-ds.yaml. However the 1.1.0 release yaml that the REAMDME.md refers to in installation instructions still references the quay.io image https://github.com/weaveworks/kured/releases/download/1.1.0/kured-1.1.0.yaml . Can releases be edited? I'm a bit ignorant here...

[cdmurph32]

Any update? This image has been unavailable for two days.

[jethrogb]

Maybe related to http://status.quay.io/incidents/4lb8mr3fmpqg

[mleneveut]

It is supposed to be resolved 4 hours ago, but I still got the issue :

docker pull quay.io/weaveworks/kured:1.1.0
Error response from daemon: Get https://quay.io/v2/weaveworks/kured/manifests/1.1.0: unknown: Namespace weaveworks has been disabled. Please contact a system administrator.

[AtulP123]

I'm getting the same error as well. I changed the tag to 1.0.0, but that didn't help either

[slynickel]

I don't know what the long term fix is but if you're using v1.1.0 it appears you should use docker.io/weaveworks/kured:1.1.0 instead.

@hiddeco or @bboreham is this correct? I see you did #69 to update the reference in the master branch to use docker.io/weaveworks/kured:1.1.0 instead of quay.io. Is that the long term solution?

If it is, it would be great if v1.0.0 be added to docker.io. For those of us still running old version of Kubernetes kured 1.1.0 doesn't work but docker.io doesn't have 1.0.0.

[hiddeco]

Hi all of you,

Unfortunately Quay.io isn't working for us at the moment. The semi-permanent solution until this has been resolved is indeed to use the docker.io/weaveworks/kured:1.1.0 image.

We have been working very hard to get our OSS images up on Docker Hub, but I am afraid 1.0.0 of Kured is not on Docker Hub yet. I will rebuild the 1.0.0 version in the next half hour and push it as 1.0.0-rebuild, please note that this image will have a different digest than the original 1.0.0 image.

My apologies for the abrupt change and any inconvenience it may (have) cause(d).

[hiddeco]

@slynickel I just made 1.0.0 available as docker.io/weaveworks/kured:1.0.0-rebuild

[slynickel]

@hiddeco thanks, much appreciated!!!

[cdmurph32]

Thanks

[moltar]

I know this is a different repo, but getting the same issues for another weaveworks image:

  Normal   Pulling      5m12s (x4 over 6m32s)  kubelet, foo-infra-1-mev3  pulling image "quay.io/weaveworks/flux:1.11.0"
  Warning  Failed       5m12s (x4 over 6m32s)  kubelet, foo-infra-1-mev3  Failed to pull image "quay.io/weaveworks/flux:1.11.0": rpc error: code = Unknown desc = Error response from daemon: Get https://quay.io/v2/weaveworks/flux/manifests/1.11.0: unknown: Namespace weaveworks has been disabled. Please contact a system administrator.
  Warning  Failed       5m12s (x4 over 6m32s)  kubelet, foo-infra-1-mev3  Error: ErrImagePull
  Normal   BackOff      4m57s (x5 over 6m31s)  kubelet, foo-infra-1-mev3  Back-off pulling image "quay.io/weaveworks/flux:1.11.0"
  Warning  Failed       88s (x20 over 6m31s)   kubelet, foo-infra-1-mev3  Error: ImagePullBackOff

[moltar]

FYI, a local docker pull is also failing...

❯ docker pull quay.io/weaveworks/flux:1.11.0
Error response from daemon: Get https://quay.io/v2/weaveworks/flux/manifests/1.11.0: unknown: Namespace weaveworks has been disabled. Please contact a system administrator.

[moltar]

fluxcd/flux#1948

[jakaruna-MSFT]

is there any update for us

[edernucci]

is there any update for us

@jakaruna-MSFT please change quay.io to docker.io in yaml.

[jakaruna-MSFT]

@edernucci Thank you.
We are using that workaround now.
We have referenced this yaml https://github.com/weaveworks/kured/releases/download/1.1.0/kured-1.1.0.yaml in our document. In that release its pointing to quay.io.
Can we update the release with docker.io

[awh]

• I have added https://github.com/weaveworks/kured/releases/download/1.1.0/kured-1.1.0-dockerhub.yaml to the 1.1.0 release, which sources the image from Dockerhub
• I have just made a 1.2.0 release which has a https://github.com/weaveworks/kured/releases/download/1.2.0/kured-1.2.0-dockerhub.yaml manifest