[TheIronYuppie]

Heh, that's true - you can't run binaries that aren't there :)

[sofaofthedamned]

Another thing - the docs state to go to https://<kubernetesIP> but that does nothing. Instead I have to go to http://kubernetesIP:30000 for the UI. Am I missing something else?

Also, using the KVM driver on Ubuntu 16.04 I have to run the start command twice to be able to bring up a pod. That's with the 'vm-driver=kvm' at the end.

Got there in the end anyways - thank you!

[sofaofthedamned]

Replying to myself here - the :443 entry seems to have a problem:

"This site can’t provide a secure connection

192.168.42.174 doesn't adhere to security standards. ERR_SSL_SERVER_CERT_BAD_FORMAT"

I assume this is related to Ubuntu/KVM related shenanigans. I'll have a go later on Mac.

[dlor]

Hey,

http://kubernetesIP/ui should work. Where in the docs did you see https://kubernetesIP ? I can get those cleaned up.

[sofaofthedamned]

In addition the VM isn't even listening on 80, it's only listening on 443 and 30000:

"Kubernetes is available at https://192.168.42.174:443. Kubectl is now configured to use the cluster. root@thinkbuntu:/root/kubernetes# nmap 192.168.42.174

Starting Nmap 7.01 ( https://nmap.org ) at 2016-07-11 22:44 BST Nmap scan report for 192.168.42.174 Host is up (0.00061s latency). Not shown: 996 closed ports PORT STATE SERVICE 22/tcp open ssh 443/tcp open https 8081/tcp open blackice-icecap 30000/tcp open unknown MAC Address: 52:54:00:C8:F1:38 (QEMU virtual NIC)

Nmap done: 1 IP address (1 host up) scanned in 25.54 seconds"

[sofaofthedamned]

It's right in the app itself:

"$ minikube start Starting local Kubernetes cluster... Running pre-create checks... Creating machine... Starting local Kubernetes cluster... Kubernetes is available at https://192.168.99.100:8443."