Created
September 5, 2016 16:51
-
-
Save kozikow/fc76d2d34ebc4f0978c617d30835a852 to your computer and use it in GitHub Desktop.
Libmachine output
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Starting local Kubernetes cluster... | |
| Running pre-create checks... | |
| Creating machine... | |
| (minikubeVM) Downloading /home/kozikow/.minikube/cache/boot2docker.iso from file:///home/kozikow/.minikube/cache/iso/minikube-0.6.iso... | |
| (minikubeVM) Creating VirtualBox VM... | |
| (minikubeVM) Creating SSH key... | |
| (minikubeVM) Starting the VM... | |
| (minikubeVM) Check network to re-create if needed... | |
| (minikubeVM) Waiting for an IP... | |
| Waiting for machine to be running, this may take a few minutes... | |
| Detecting operating system of created instance... | |
| Waiting for SSH to be available... | |
| Detecting the provisioner... | |
| Provisioning with boot2docker... | |
| 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. | |
| Checking connection to Docker... | |
| 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. | |
| Kubectl is now configured to use the cluster. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment