Skip to content

Instantly share code, notes, and snippets.

@dimorinny

dimorinny/docker-machine logs

Created June 3, 2016 18:12
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save dimorinny/774fcbf20d08cc716489f688e8cfb388 to your computer and use it in GitHub Desktop.
Save dimorinny/774fcbf20d08cc716489f688e8cfb388 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
docker-machine logs
(test13) DBG | Matching pattern for code="ProvisioningState/succeeded"
(test13) DBG | Matching pattern for code="PowerState/running"
(test13) DBG | Power state found.
(test13) DBG | Determined Azure PowerState="running", docker-machine state="Running"
(test13) DBG | Machine IP address resolved to: 40.64.209.171
(test13) DBG | Machine URL is resolved to: tcp://40.64.209.171:2376
Reading CA certificate from /Users/Dimorinny/.docker/machine/certs/ca.pem
Reading server certificate from /Users/Dimorinny/.docker/machine/machines/test13/server.pem
Reading server key from /Users/Dimorinny/.docker/machine/machines/test13/server-key.pem
Error creating machine: Error checking the host: Error checking and/or regenerating the certs: There was an error validating certificates for host "40.68.209.171:2376": remote error: bad certificate
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.
open : no such file or directory
notifying bugsnag: [Error creating machine: Error checking the host: Error checking and/or regenerating the certs: There was an error validating certificates for host "40.68.209.171:2376": remote error: bad certificate
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment