bash: : command not found anadda ~ $ regenerate-certs test Regenerate TLS machine certs? (y/n): y Regenerating TLS certificates Waiting for SSH to be available... anadda ~ $ eval $(env test) anadda ~ $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES anadda ~ $ This fix is actually a lot easier then most may think especially if you're using a Linux distribution like Ubuntu.Without sudo - [[email protected] vagrant]$ docker version Client: Version: 1.12.1 API version: 1.24 Go version: go1.6.3 Git commit: 23cf638 Built: OS/Arch: linux/amd64 Cannot connect to the Docker daemon. With sudo - [[email protected] ~]$ sudo docker version Client: Version: 1.12.1 API version: 1.24 Go version: go1.6.3 Git commit: 23cf638 Built: OS/Arch: linux/amd64 Server: Version: 1.12.1 API version: 1.24 Go version: go1.6.3 Git commit: 23cf638 Built: OS/Arch: linux/amd64 Docker commands require sudo or to be run as root, many forget this and end up restarting or creating their default machine over and over again.

anadda ~ $ eval `"$(docker-machine env test)"` Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.76": x509: certificate is valid for 192.1, not 192.1 You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'. Setting Docker configuration on the remote daemon...

Be advised that this will trigger a Docker daemon restart which will stop running containers. anadda ~ $ anadda ~ $ ls NAME ACTIVE DRIVER STATE URL SWARM DOCKER ERRORS test - virtualbox Running tcp://192.76 v1.12.0 default - virtualbox Stopped Unknown anadda ~ $ docker ps An error occurred trying to connect: Get open //./pipe/docker_engine: The system cannot find the file specified.

The Diagnostic channel will then start collecting data relevant to a join or create operation. With the new features of Server 2012 Failover Clustering, the cluster will be created in the same organizational unit (OU) as the nodes.

For example, suppose you previously enabled the Diagnostic channel and you're having a problem creating a cluster. For the cluster name to be created, the logged-on user must have at least Read and Create Computer Objects permissions.

If the machine is already running, it skips the start command and will fix the environment variables of the current shell.

is not necessary every single time you open up a new terminal.Knowing the purpose of each event channel can help you find the errors more quickly, which in turn will help you troubleshoot the problem more quickly.Here's an explanation of each channel: Because administrators often encounter problems when creating clusters and joining nodes, I want to show you how to use the Failover Clustering-Client/Diagnostic channel.As @reklis mentioned, you just need to check if the machine is not running and start it only in that case.Something along the lines of: I have Mac OS X and docker tray application is saying that docker is running, but on console it is saying it is not. For me it looks like some ghost enviroinent is creating by docker and is used by default.To view the data collected, you need to right-click the channel and choose Disable Log. Event ID: 2 Level: Error Description: Create Cluster Name COIf Not Exists (6879): Failed to create computer object CLUSTER on DC \DC. If the user doesn't have those rights, the name won't be created and you'll receive this type of error.