-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Improve error handling on ARM architectures #7818
Comments
Sorry about that. Do you mind sharing the output of:
It would also be useful to know if using the latest beta fixes this issue for you: https://github.com/kubernetes/minikube/releases/tag/v1.10.0-beta.0 Thank you for the report! |
I'm marking this as a bug, because whatever the underlying root cause is here, our error handling is clearly not very good. |
Thanks a lot, here it is:
|
I think it is related to go-containerregistry not supporting architectures properly...
The $ docker inspect gcr.io/k8s-minikube/kicbase:v0.0.8 | grep Arch
"Architecture": "amd64", |
@LyleLee : only the
@tstromberg : that seems right |
Should add some arch checks, to the documentation and to the code. See #6159 |
@afbjorklund Thanks for point out the clue. I'd try build gcr.io/k8s-minikube/kicbase from Dockerfile rather than pull it from registry.
|
Update:
But those images referred in documentation is not built for ARM64, like: Can we start to push ARM64 images? I would like to help out if I know the routine to publish these images. |
Currently docker driver doesn't support ARM yet. we need to have better solution message to let the users nicely. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Can anyone instruct me a little bit about what is going on? I am working with:
Steps to reproduce the issue:
Full output of failed command:
Full output of
minikube start
command used, if not already included:As above.
Optional: Full output of
minikube logs
command:The text was updated successfully, but these errors were encountered: