-
Notifications
You must be signed in to change notification settings - Fork 751
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MinIO addon] console pod goes into ImagePullBackOff #4511
Comments
Hi @deusebio, Thanks for reporting this issue. I'll be working on getting this fixed. |
I am also facing same issue. is there any work around? When will it get fixed? |
minio/console#3318 - they no longer upload images for console since it's now part of minio/minio same binary |
Confirmed I see this too |
Hi everyone, The minio team has deleted the console image from Dockerhub, which is problematic for the minio addon because it uses v4.5 of the minio-operator which relies on the console image. A temporary workaround is to find another source for the console image (eg. quay.io/minio/console) and modify the deployments so they use this image instead of just minio/console. For a new cluster, you can replace line 89 of Please note that these workarounds are not officially supported by Canonical, and the Microk8s team will be upgrading the minio addon version in the next patch release of Microk8s. |
Summary
When enabling MinIO addon on MicroK8s 1.28-strict, the console pod never starts because of a ImagePullBackOff error due to the fact that it is unable to download the
minio/console
image from docker. I checked on DockerHub, and indeed, theminio/console
page (which is indexed by google) does not seem to exist anymore.Here is the
kubectl describe
command outputThe console pod is then on a ImagePullBackOff error loop
What Should Happen Instead?
The console pod should just start fine.
Reproduction Steps
Introspection Report
inspection-report-20240423_091630.tar.gz
Can you suggest a fix?
I'm wondering whether the MinIO console image has been pulled out from DockerHub or if it got moved. If it was pull out and there is not alternative, we should probably either publish a Canonical supported one to have more control over it or disable the console to be run by default.
Are you interested in contributing with a fix?
If provided with guidance, I could give it a try. But I've never dug in the MicroK8s codebase, so if it's not a good-first issue (and given that this seems a bit critical/impactful to everyone using MinIO), maybe I'm not the best bet.
The text was updated successfully, but these errors were encountered: