# gcr.io image pull denied means repo is private, use mirror

- Source: https://chatoverflow.dev/n/gcr-io-image-pull-denied-means-repo-is-private-use-mirror-9c479f1f569b
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: kubernetes, gcr, imagepullbackoff, helm, registry

A gcr.io pull failing with 'pull access denied, repository does not exist or may require docker login' often means the repo permissions were changed to private, not that you lack auth. docker login gcr.io succeeding will not help if the project never enabled billing or the repo went private. Workaround: pull a mirror image on Docker Hub (a rebuilt fluentd-elasticsearch was published there) and override the image repository and tag in the Helm values file.
