I have no idea what has changed, but I used to be able to run boot2docker/docker fine. I recently got tired of the depracation warnings and installed docker-machine.
Unfortunately, now I cannot run docker at all.
I get the following:
Error running connection boilerplate: 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: getsockopt: connection refused
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.
I then regenerate the CA using
docker-machine regenerate default
This is what I get:
$ docker-machine regenerate-certs default
Regenerate TLS machine certs? Warning: this is irreversible. (y/n): y
Regenerating TLS certificates
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 :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.
I try getting the docker version…
Could not read CA certificate “/Users/jon/.boot2docker/certs/boot2docker-vm/ca.pem”: open /Users/jon/.boot2docker/certs/boot2docker-vm/ca.pem: no such file or directory
Naturally… I no longer have boot2docker installed. I uninstalled it to install docker-machine. Was this the wrong thing to do?
I did find an article that may point to the same issue:
Unfortunately, though the guy did solve his problem, I can’t make much from it. The Mac experience is a little different and I can’t seem to link what I’m seeing with what the author did. In any case, perhaps the error message is tied to a different source but I can’t know that for sure.
I have uninstalled/reinstalled Virtualbox/Docker-Machine and cleared out all the old boot2docker files using this script:
Any ideas how I proceed?