search

sparkfabrik / sparkdock

Automatic MacOS system provisioning
Other
20 stars 8 forks source link

[SOLVED] Unable to query docker version: Get https://192.168.99.100:2376/v1.15/version: x509: certificate is valid for 192.168.99.102, not 192.168.99.100 #14

Closed g0blin79 closed 4 years ago

g0blin79 commented 7 years ago

Hi to all.

at the end of the installation process, if i launched a docker-machine ls I had this:

NAME     ACTIVE   DRIVER       STATE     URL                         SWARM   DOCKER    ERRORS
dinghy   *        virtualbox   Running   tcp://192.168.99.100:2376           Unknown   Unable to query docker version: Get https://192.168.99.100:2376/v1.15/version: x509: certificate is valid for 192.168.99.102, not 192.168.99.100

I solved in this way:

$ docker-machine regenerate-certs dinghy

I don't know if could be useful to add something like this into the README. I would leave notice of that.

BTW: What fu***ng piece of code!!

tuxisma commented 7 years ago

thanks a lot! It worked for me.

rebepoi commented 7 years ago

Worked for me too! Life saver!

steevehook commented 6 years ago

Thanks man. really weird. Happened to me after I rebooted my machine

liuqiqi1 commented 6 years ago

iptables

dev120285 commented 6 years ago

While working with GIT Bash I had to regenerate ,once I switched back to Power Shell same effort was required. docker-machine regenerate-certs myvm1

chinmay90kulkarni commented 6 years ago

Worked for me as well.. thanks

liuweiming1997 commented 6 years ago

I am so sad because it not work for me, it still sunday generic Timeout

by

➜ ~ docker-machine regenerate-certs sunday Regenerate TLS machine certs? Warning: this is irreversible. (y/n): y Regenerating TLS certificates Waiting for SSH to be available... Detecting the provisioner... Installing Docker... Copying certs to the local machine directory... Copying certs to the remote machine... Setting Docker configuration on the remote daemon...

dev120285 commented 6 years ago

Try with --force param

liujunberg commented 6 years ago

It does work to me, thanks

iplanetcn commented 6 years ago

This works for me, thank you. But it produces a new question, the docker-machine's IP address changed. Is there a good way (without changing the IP address)?

will-hu-0 commented 6 years ago

Works for me as well, thanks!

lmbautista commented 6 years ago

EC2 working again! Thanks!!! 🤓

koksin commented 6 years ago

thanks It solved my problem. works like a charm..

amirghoul commented 5 years ago

thanks a lot <3

pdsiaj commented 5 years ago

it didn't work for me, despite using force at the end, what other way can we try to rectify this please

jerryguowei commented 5 years ago

thanks, it works for me

remycerigny commented 5 years ago

Work for me too ! Thanks a lot mate :)

ismbabuIBM commented 5 years ago

Works for me as well.. Thanks!

AbilioSouza commented 4 years ago

thanks, it works for me

archVille commented 4 years ago

Hi to all.

at the end of the installation process, if i launched a docker-machine ls I had this:

NAME     ACTIVE   DRIVER       STATE     URL                         SWARM   DOCKER    ERRORS
dinghy   *        virtualbox   Running   tcp://192.168.99.100:2376           Unknown   Unable to query docker version: Get https://192.168.99.100:2376/v1.15/version: x509: certificate is valid for 192.168.99.102, not 192.168.99.100

I solved in this way:

$ docker-machine regenerate-certs dinghy

I don't know if could be useful to add something like this into the README. I would leave notice of that.

BTW: What fu***ng piece of code!!

worked for me too. Nice!

charlesgres commented 3 years ago

You may need to add the --client-certs option:

docker-machine regenerate-certs --client-certs dinghy

ThatcherT commented 3 years ago

Worked for me!