Stuck while creating the VMs in Virtual box using vagrant up

Kubernetes
#1

Got stuck and getting the following message while creating virtual machine using vagrant up

controlplane: Which interface should the network bridge to?

I have provided following answers
ethernet adapter
wireless lan adapter
wireless lan adapter wi-fi
Wi-Fi adapter
Ethernet adapter Ethernet 2
But still I am getting the same question

#2

What vagrant script are you using, and what platform are you running it on? If you’re using the vagrant script from the CKA archive (on Windows – it doesn’t work on MacOS), I’d need a bit more info to tell you want’s up here.

#3

I downloaded the vagrant script from the following the github repo

#4

I am using this script on windows 11 machine
Script Execution

PS C:\devops\kodeadm\certified-kubernetes-administrator-course\kubeadm-clusters\virtualbox> vagrant up
Bringing machine ‘controlplane’ up with ‘virtualbox’ provider…
Bringing machine ‘node01’ up with ‘virtualbox’ provider…
Bringing machine ‘node02’ up with ‘virtualbox’ provider…
==> controlplane: Importing base box ‘ubuntu/jammy64’…
==> controlplane: Matching MAC address for NAT networking…
==> controlplane: Setting the name of the VM: controlplane
==> controlplane: Clearing any previously set network interfaces…
==> controlplane: Specific bridge ‘Intel(R) Wi-Fi 6E AX211 160MHz’ not found. You may be asked to specify
==> controlplane: which network to bridge to.
==> controlplane: Available bridged network interfaces:
==> controlplane: When choosing an interface, it is usually the one that is
==> controlplane: being used to connect to the internet.
==> controlplane:
controlplane: Which interface should the network bridge to?

#5

I am using this script on windows 11 machine

#6

Hi Rob

I resolved this issus. Able to install all three VM’s in virtual box using vagrant script only.
First issue was with my Virtual box installation. I did the installation again and then in vagrant script file I changed the build_mode to “NAT”.

#7

Not sure why the script failed to figure out your specific network configuration, but using the NAT setting in the script is just fine if you don’t need bridging. If you decide you do, ask, since the guy who wrote the script is a pretty good Windows engineer.