-
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
docker: start fails on storage provisioner addon "x509: certificate is valid for 172.17.0.3" #8936
Comments
@srilumpa thank you for reporting this, does this happen consistantly or is it a flake? I believe this is because the docker container IP was changed
I believe once we have a static IP for docker containers this error should not happen. |
this PR might fix this issue #8764 but I am still puzzled why we had not seen this issue more often if that is an IP change problem. |
/triage needs-information |
@medyagh, thank you for your time on this. Yes, running |
I belive this could result of the the IP change after minikube restart that could be fixed by static IP PR |
the PR fixing this bug is still under works. |
Steps to reproduce the issue:
In my setup, it seems that minikube changes of IP address between startups. This makes the enabling of some addons failing because the certificate is seen as invalid.
The only way for me to be able to start minikube again is to either restart my workstation (and this does not always fix the issue) or to delete my minikube instance an recreate it.
Full output of failed command:
Full output of
minikube start
command used, if not already included:Optional: Full output of
minikube logs
command:The text was updated successfully, but these errors were encountered: