sealed-secrets: Unable to find container images
I am not able to install sealed-secrets anymore. Using helm chart (v2.1.5), my k8s cluster is not able to find the container image:
13s Normal Pulling pod/sealed-secrets-controller-5d8db499cd-zthst Pulling image "quay.io/bitnami/sealed-secrets-controller:v0.17.4"
12s Warning Failed pod/sealed-secrets-controller-5d8db499cd-zthst Failed to pull image "quay.io/bitnami/sealed-secrets-controller:v0.17.4": rpc error: code = Unknown desc = reading manifest v0.17.4 in quay.io/bitnami/sealed-secrets-controller: unauthorized: access to the requested resource is not authorized
Shouldn’t there be a repository at https://quay.io/repository/bitnami/sealed-secrets-controller? Currently you are forced to login to quay.io and then it says “No repository found”.
It seems that the sealed-secrets image repository has been deleted?
docker pull quay.io/bitnami/sealed-secrets-controller:v0.17.4
Error response from daemon: unauthorized: access to the requested resource is not authorized
Solution
Update the sealed-secrets-controller repository to our new oficial dockehub location:
image:
registry: docker.io
repository: bitnami/sealed-secrets-controller
See https://github.com/bitnami-labs/sealed-secrets/issues/822#issuecomment-1105307200
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 79
- Comments: 37 (7 by maintainers)
Commits related to this issue
- Update url for img controller Updated the URL for the bitnami sealed-secrets-controller redirecting to docker instead of quay. Linked issue: https://github.com/bitnami-labs/sealed-secrets/issues/82... — committed to codefresh-contrib/gitops-certification-examples by deleted user 2 years ago
- fix: container image location bitnami-labs/sealed-secrets#822 — committed to opencdk8s/cdk8s-sealed-secrets-controller by Hunter-Thompson 2 years ago
- services.setup: Pull Grafana image from docker.io Bitnami recently stopped publishing their images on quay.io after becoming a verified publisher on Dockerhub. Verified publishers are not subject to... — committed to cockpit-project/bots by allisonkarlitskaya 2 years ago
- Upgrade sealed secrets from v1 to v2 Fixes https://github.com/bitnami-labs/sealed-secrets/issues/822 — committed to argoflow/argoflow-gcp by haoxins 2 years ago
- services.setup: Pull Grafana image from docker.io Bitnami recently stopped publishing their images on quay.io after becoming a verified publisher on Dockerhub. Verified publishers are not subject to... — committed to cockpit-project/bots by allisonkarlitskaya 2 years ago
- services.setup: Pull Grafana image from docker.io Bitnami recently stopped publishing their images on quay.io after becoming a verified publisher on Dockerhub. Verified publishers are not subject to... — committed to cockpit-project/bots by allisonkarlitskaya 2 years ago
- services.setup: Pull Grafana image from docker.io Bitnami recently stopped publishing their images on quay.io after becoming a verified publisher on Dockerhub. Verified publishers are not subject to... — committed to cockpit-project/bots by allisonkarlitskaya 2 years ago
- Update redis helm chart values Update to the correct image registry in order to fix the bug that occured when deploying redis Image registry has change from quay.it to docker.io - explanation - https... — committed to idoburstein/notify-service by idoB123 2 years ago
- Update redis helm chart values Update to the correct image registry in order to fix the bug that occured when deploying redis. Image registry has change from quay.it to docker.io - explanation - http... — committed to idoburstein/notify-service by idoB123 2 years ago
- Update redis helm chart values Update to the correct image registry in order to fix the bug that occured when deploying redis. Image registry has change from quay.it to docker.io - explanation - http... — committed to idoburstein/notify-service by idoB123 2 years ago
- Update redis helm chart values Update to the correct image registry in order to fix the bug that occured when deploying redis. Image registry has change from quay.it to docker.io - explanation - htt... — committed to idoburstein/notify-service by idoB123 2 years ago
- Update controller.yaml changed to docker.hub https://github.com/bitnami-labs/sealed-secrets/issues/822#issuecomment-1104116084 — committed to cdjg35/gitops-certification-examples by cdjg35 2 years ago
- someone screwed up bitnami images on quay.io https://github.com/bitnami-labs/sealed-secrets/issues/822 — committed to Aman1994/k8id by ashish1099 2 years ago
- someone screwed up bitnami images on quay.io https://github.com/bitnami-labs/sealed-secrets/issues/822 — committed to Obmondo/kubeaid by ashish1099 2 years ago
- someone screwed up bitnami images on quay.io https://github.com/bitnami-labs/sealed-secrets/issues/822 — committed to Obmondo/kubeaid by ashish1099 2 years ago
Hi everyone,
The new controller image is already available from the new oficial DockerHub repository: https://hub.docker.com/r/bitnami/sealed-secrets-controller/tags
The reason for this change is to use our Dockerhub Bitnami account as a distribution platform of the controller image. Doing so we can leverage in the advantages of being a verified publisher, such as not been affected by dockerhub pull rate limits.
Unfortunately, quay.io could not provide that level of support for our images and we were forced to migrate the images.
Please accept our apologies if this action has created some disturbances during the process. Regards
Hi everyone,
A quick update on this task: we have uploaded the sealed-secrets controller images from previous versions in our Dockerhub oficial repository. The full list of available versions is:
This covers versions older than 2,5 years (and, again, we cannot recommend the use of releases so outdated). As a bonus, the controller binary has being compiled with our latest supported go version, which means a more efficient binary on most cases.
Restoring the controller is just a matter of updating the chart value accordingly:
We will pin this issue for future reference and mark it as closed in the following days.
Regards!
Older images that were on quay.io are not accessible on quay or dockerhub right now, impacting our production systems. Where can we reference older versions?
We are investigating the best way to publish older versions of the controller in the new DockerHub repository.
However, we fully recommend upgrading your clusters to the newest release (v.0.17.5) Upgrading should be quite straightforward and older versions of sealed secrets will not have our latest improvements and bugfixes.
https://github.com/bitnami-labs/sealed-secrets/pull/824 - prepare for a new release on a different repo I guess.
The new docker image, tagged as v0.17.5 and uploaded to dockerhub, works for me.
@agarcia-oss,@alvneiayu Thanks for fixing it.
You can watch GitHub actions - e.g. https://github.com/bitnami-labs/sealed-secrets/runs/6096838026?check_suite_focus=true
@pigfrown you need to first run
make controllerwhich creates the controller binarythen you can copy it to the correct directory in dist/ and build the image