Skip to content

Conversation

@alpeb
Copy link
Member

@alpeb alpeb commented Feb 11, 2026

For the past few days, pulling gcr.io/google_containers/pause:3.2 has failed sporadically:

$ docker pull gcr.io/google_containers/pause:3.2
Error response from daemon: unknown: failed to resolve reference "gcr.io/google_containers/pause:3.2": unexpected status from HEAD request to https://gcr.io/v2/google_containers/pause/manifests/3.2: 400 Bad Request

Also Artifact Hub scanning is failing:

error scanning image gcr.io/google_containers/pause:3.2: error running trivy on image gcr.io/google_containers/pause:3.2: 2026-02-11T18:45:49Z FATAL Fatal error run error: image scan error: scan error: scan failed: failed analysis: unable to get the image ID: unable to get the image ID: GET https://gcr.io/v2/google_containers/pause/blobs/sha256:80d28bedfe5dec59da9ebf8e6260224ac9008ab5c11dbbe16ee3ba3e4439ac2c: NAME_INVALID: Request contains an invalid argument.

(package linkerd-multicluster:2025.10.6)

It appears the gcr.io/google_containers registry is no longer favored and instead the registry.k8s.io has been what's officially supported, so we're switching to that one.

For the past few days, pulling `gcr.io/google_containers/pause:3.2` has
failed sporadically:

```
$ docker pull gcr.io/google_containers/pause:3.2
Error response from daemon: unknown: failed to resolve reference "gcr.io/google_containers/pause:3.2": unexpected status from HEAD request to https://gcr.io/v2/google_containers/pause/manifests/3.2: 400 Bad Request
```

Also Artifact Hub scanning is failing:

```
error scanning image gcr.io/google_containers/pause:3.2: error running trivy on image gcr.io/google_containers/pause:3.2: 2026-02-11T18:45:49Z FATAL Fatal error run error: image scan error: scan error: scan failed: failed analysis: unable to get the image ID: unable to get the image ID: GET https://gcr.io/v2/google_containers/pause/blobs/sha256:80d28bedfe5dec59da9ebf8e6260224ac9008ab5c11dbbe16ee3ba3e4439ac2c: NAME_INVALID: Request contains an invalid argument.

(package linkerd-multicluster:2025.10.6)
```

It appears the `gcr.io/google_containers` registry is no longer favored
and instead the `registry.k8s.io` has been what's [officially
supported](https://kubernetes.io/blog/2022/11/28/registry-k8s-io-faster-cheaper-ga/),
so we're switching to that one.
@alpeb alpeb requested a review from a team as a code owner February 11, 2026 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants