You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error:
... FAIL E1216 18:22:49.047095 3027 start.go:499] Error starting the VM: Error creating the VM. Error creating machine: Error checking the host: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.56.104:2376": dial tcp 192.168.56.104:2376: connect: network is unreachable
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.
. Retrying.
Error starting the VM: Error creating the VM. Error creating machine: Error checking the host: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.56.104:2376": dial tcp 192.168.56.104:2376: connect: network is unreachable
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.
Trying to ssh connect to the Docker daemon on port 2376 from inside the MiniShift Linux VM daemon fails:
[docker@minishift .ssh]$ ssh -vvv -p 2376 192.168.56.104
OpenSSH_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 58: Applying options for *
debug2: resolving "192.168.56.104" port 2376
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to 192.168.56.104 [192.168.56.104] port 2376.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /home/docker/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/docker/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/docker/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/docker/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/docker/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/docker/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/docker/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/docker/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.4
debug1: ssh_exchange_identification: \025\003\001
ssh_exchange_identification: Connection closed by remote host
[docker@minishift .ssh]$
It seems something wrong with a certificate but don't know which are used where.
Googling this error gave me "it's because the IP has changed", but no IP address has changed AFAIK.
macOS host 192.168.197.10
Linux VM eth1 192.168.56.104
"minishift delete -f" does not solve the issue.
Maybe not related: I've created the file /etc/vbox/networks.conf to allow 192.168.99.0/24.
General information
Steps to reproduce
Expected
minishift starts successfully.
Actual
Error:
... FAIL E1216 18:22:49.047095 3027 start.go:499] Error starting the VM: Error creating the VM. Error creating machine: Error checking the host: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.56.104:2376": dial tcp 192.168.56.104:2376: connect: network is unreachable
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.
. Retrying.
Error starting the VM: Error creating the VM. Error creating machine: Error checking the host: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.56.104:2376": dial tcp 192.168.56.104:2376: connect: network is unreachable
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.
Trying to ssh connect to the Docker daemon on port 2376 from inside the MiniShift Linux VM daemon fails:
[docker@minishift .ssh]$ ssh -vvv -p 2376 192.168.56.104
OpenSSH_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 58: Applying options for *
debug2: resolving "192.168.56.104" port 2376
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to 192.168.56.104 [192.168.56.104] port 2376.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /home/docker/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/docker/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/docker/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/docker/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/docker/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/docker/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/docker/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/docker/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.4
debug1: ssh_exchange_identification: \025\003\001
ssh_exchange_identification: Connection closed by remote host
[docker@minishift .ssh]$
It seems something wrong with a certificate but don't know which are used where.
Googling this error gave me "it's because the IP has changed", but no IP address has changed AFAIK.
macOS host 192.168.197.10
Linux VM eth1 192.168.56.104
"minishift delete -f" does not solve the issue.
Maybe not related: I've created the file /etc/vbox/networks.conf to allow 192.168.99.0/24.
Logs
$ ./minishift start --show-libmachine-logs -v5
https://gist.github.com/efixp/2c0d132f3a40b3d48fe8ae95e0f83386)
Thanks for any hints.
The text was updated successfully, but these errors were encountered: