Type checking interface for veth breaks container startup on 1.15.0 and 1.16.0 images, causes issues w/ ipvlan and macvlan networks.

[MxD-js]

Hi, This line here causes ipvlan network issues, docker sets the network type toipvlan in the container and this check fails and never moves past this loop when a image is restricted to a ipvlan type network per kasm documentation. Removing the veth check or adding ipvlan to the type check resolves this issue. This works fine if the image is on the kasm_default_network because docker sets the interface type to vethbut breaks when the container is restricted to ipvlan or macvlan networks.

Curious why the strict check for veth?

workspaces-core-images/src/common/startup_scripts/vnc_startup.sh

Line 446 in 41de61b

interfaces=$(ip link show type veth | awk -F: '/^[0-9]+: / {print $2}' | awk '{print $1}' | sed 's/@.*//')

issue thread for context and resolution.
kasmtech/workspaces-issues#615

[jcbshw]

Thanks for the discovery. I was also experiencing this after setting up IPVlan using the official Kasm documentation.

Making the changes locally to vnc_startup.sh resolves the issue.