What are the eight life cycle hook functions of Vue>>>
When we want to execute Eval $(docker machine Env)
to load the environment variables of the docker server, the following error appears:
Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.99.100:2376": dial tcp 192.168.99.100:2376: i/o timeout
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which will stop running containers.
According to the prompt, we execute docker machine regional certs
, this prompt:
Regenerate TLS machine certs? Warning: this is irreversible. (y/n): y
Regenerating TLS certificates
Waiting for SSH to be available...
Detecting the provisioner...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
This machine has been allocated an IP address, but Docker Machine could not
reach it successfully.
SSH for the machine should still work, but connecting to exposed ports, such as
the Docker daemon port (usually <ip>:2376), may not work properly.
You may need to add the route manually, or use another related workaround.
This could be due to a VPN, proxy, or host file configuration issue.
You also might want to clear any VirtualBox host only interfaces you are not using.
It still doesn’t seem to work. It still can’t connect to the server. Can the server be connected?You can use docker machine SSH
! Let’s restart docker machine restart
to try. Still not
What should we do?After a search, many people have had this problem, and the situation is basically the same as mine – the network segment of the docker server (virtual machine) overlaps with that of other network cards, resulting in the failure to connect
In my case, the network segment of the home router overlaps with the default network segment used in docker machine create
, so every time I go home and return to the company, I will find that the docker is useless. At first, I can only delete and rebuild the virtual machine. Later, I found the following three solutions:
Turn off TLS check. Not recommended
Specify other network segments when creating virtual machine: docker machine create - D VirtualBox -- VirtualBox hostonly CIDR "192.168.90.1/24" default
Modify the network segments of other network cards, delete the network card used by docker virtual machine, and then execute docker machine start
, which will rebuild the network card
Similar Posts:
- How to fix VirtualBox session error: Call to NEMR0InitVMPart2 failed VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED)
- “This computer doesn’t have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory”
- [How to]docker http: server gave HTTP response to HTTPS client
- VirtualBox: How to Enable Nested VT-x/AMD-V
- When Docker installs an Mirror: failed to get default registry endpoint from daemon
- Description and temporary solution of VirtualBox 5.0. X unable to connect to Internet after installation
- The most annoying error reported by Hadoop: running VirtualBox prompts 0x00000000 error “the 0x00000000 memory referenced by the 0x00000000 instruction cannot be written?
- How to Solve Vagrant Start Error
- Vagrant: How to Change the Default SSH Port
- [Solved] http: server gave HTTP response to HTTPS client