search

rancher / old-vm

(OBSOLETE) Package and Run Virtual Machines as Docker Containers
Apache License 2.0
646 stars 133 forks source link

VM Pod creation fails (Target interface does not exist) #102

Open urabenst opened 6 years ago

urabenst commented 6 years ago

Hi all,

I am using RancherVM but I can't start any VMs, since there is always an error during the creation of the pod. This is the output of kubectl logs for one of my VM pods: logs.txt At the very end it reports that Target interface ens33 does not exist. How can I fix that?

I am running k8s version 1.10.3 on Ubuntu 16.04 btw.

Thanks for having a look! Ulrich

trenton42 commented 6 years ago

I just ran into this as well. It looks like RacherVM assumes there will be a interface at ens33, but most likely your system (like mine) uses newer predictable network interface names. I think there should be some changes made in RacherVM to allow configuration of interface names per node as it may be possible that they are not the same across the cluster.

theagent commented 6 years ago

Same issue on my installation. Running Ubuntu 16.04 on the nodes and my interfaces are definitely not ens33. Actually a mixed bag of tricks in my cluster. Have a few with the old eth0 nomenclature and others with enp1s0 on others.

ApolloMission commented 6 years ago

Same issue too. Tried renaming the interface within the deploy yaml from ens33 to ens4 (the default on my google compute instance) - results in the network for that node going down.

Funny story, after a little while it then tries to deploy to another node, taking that one down too.

trenton42 commented 6 years ago

I was able to get RancherVM working by hackily detecting the Ethernet device available each time the image is launched. The image I used is on docker hub under trenton/vm. You can test RancherVM by changing the image in your ranchervm-controller deployment (in the ranchervm-system namespace). But please don't use that image for anything important, as I won't be maintaining it.

traam commented 5 years ago

@trenton42 I still have the same issue even after using your image for the vm-controller trenton/vm. My k8s cluster is running in aws and complains that "ens33 interface does not exist."

Any ideas?

trenton42 commented 5 years ago

@traam Sorry, I haven't looked at this in a while. We didn't end up using this project.

traam commented 5 years ago

Thanks @trenton42 . What do you end up for running legacy VMs in a container envt? Curious to know as I am doing a PoC.

trenton42 commented 5 years ago

We pivoted away from running the VMs in a container environment for now, so nothing at the moment :disappointed: