search

machine-drivers / docker-machine-driver-vmware

Docker machine driver for VMware Fusion and Workstation.
https://www.vmware.com/products/personal-desktop-virtualization.html
Apache License 2.0
184 stars 47 forks source link

Machine didn't return an IP #19

Closed falsandtru closed 3 years ago

falsandtru commented 5 years ago

On Ubuntu 18.04 on VMware WS, vmware driver doesn't work

$ sudo minikube start --vm-driver vmware
😄  minikube v0.34.1 on linux (amd64)
🔥  Creating vmware VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
💣  Unable to start VM: create: Error creating machine: Error in driver during machine creation: Machine didn't return an IP after 120 seconds, aborting

but kvm2 does work.

$ sudo minikube start --vm-driver kvm2
😄  minikube v0.34.1 on linux (amd64)
🔥  Creating kvm2 VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
📶  "minikube" IP address is 192.168.39.155
🐳  Configuring Docker as the container runtime ...
✨  Preparing Kubernetes environment ...
💾  Downloading kubeadm v1.13.3
💾  Downloading kubelet v1.13.3
🚜  Pulling images required by Kubernetes v1.13.3 ...
🚀  Launching Kubernetes v1.13.3 using kubeadm ... 
🔑  Configuring cluster permissions ...
🤔  Verifying component health .....
💗  kubectl is now configured to use "minikube"
🏄  Done! Thank you for using minikube!

Should I use kvm2 instead?

falsandtru commented 5 years ago

I found microk8s. I'll try to use it.

gbraad commented 5 years ago

If no IP, check your network setup. You have to allow DHCP, else the machine will never get a usable address.

On Mon, Feb 18, 2019, 01:20 falsandtru notifications@github.com wrote:

I found microk8s. I'll try to use it.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/machine-drivers/docker-machine-driver-vmware/issues/19#issuecomment-464483680, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAHZiA0n5MJ5jZBsWZS1_MKlXgsEQAXks5vOY9TgaJpZM4a_qPO .

falsandtru commented 5 years ago

But kvm2 can get an IP. Can you resolve in the same way?

gbraad commented 5 years ago

The virtual networking stacks of KVM and VMware are different. I persoanlly do not use VMware, but I would suggest testing the setup of the virtual network devices... use a VM other than minikube or minishift and confirm it works with DHCP.

On Mon, Feb 18, 2019 at 1:58 AM falsandtru notifications@github.com wrote:

But kvm2 can get an IP. Can you resolve in the same way?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/machine-drivers/docker-machine-driver-vmware/issues/19#issuecomment-464551911, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAHZt5yE6NpSRWagIJkYMuNnM2E5iaKks5vOgjggaJpZM4a_qPO .

--

Gerard Braad | http://gbraad.nl [ Doing Open Source Matters ]

LeetaoGoooo commented 5 years ago

@gbraad @falsandtru any example for enable dhcp? if dhcp server's ip is docker0's ip and handware is also docker0's too?

gbraad commented 5 years ago

As mentioned, I do not use VMWare and have no means to test this at the moment. It really depends on how Workstation sets up networking, but I do believe a NAT based solution would provide DHCP... if not, sorry... can help you there now.

LeetaoGoooo commented 5 years ago

any way,thank you~😀

EfraimLA commented 5 years ago

I've the same issue, sadly cannot use other vmdriver or hypervisor, isn't there solution?

mikeroySoft commented 3 years ago

This should be resolved in v0.1.3. Feel free to re-open this issue if you find it isn't =)