Was doing a
docker-machine env default
where it seems to be getting stuck (waiting longer than usual) and when I open Virtualbox and look at the preview, it is already initialized and ready to accept commands but my terminal command is still waiting.
Then when I exit (e.g. Ctrl+C or Cmd+C) this error will show up.
open /Users/yourUsername/.docker/machine/machines/default/ca.pem: no such file or directory
The error could also be
Daemon not responding yet: dial tcp : xxx operation timed out
These resolved it for me.
docker-machine regenerate-certs default
docker-machine restart default
I was not using existing/custom certificates and letting Docker Toolbox create/manage it and willing to loose any information in that virtual/docker-machine. It should be true for most people but if you use custom certificates or don’t let docker-machine manage it for you, this will not apply to you and you need to find answers elsewhere.
There is also some references that AnyConnect (VPN) + your Virtualbox Networking Settings could cause it so if these do not work, try turning it off as well. Then find out more about VirtualBox networking settings. If you must be in VPN then
> you can use this script (while on VPN) – script found here – it will fix routes/rules that gets changed by AnyConnect
* Docker Toolbox
The post .docker/machine/machines/default/ca.pem: no such file or directory appeared first on Ryan Garaygay.