Hi everyone, has anybody run into this issue when using kubeadm (VirtualBox + Va . . .

Kubernetes-Slack Discussions
#21

Bashar:
The specified host network collides with a non-hostonly network!
This will cause your specified IP to be inaccessible. Please change
the IP or name of your host only network so that it no longer matches that of
a bridged or non-hostonly network.

Bridged Network Address: ‘192.168.0.0’
Host-only Network ‘enp0s3’: ‘192.168.0.0’

#22

Bashar:
I think my CPU resources are not correct as I see there is only one CPU
image.png

#23

Bashar:
as you can see there is only 1 CPU. it might be the issue? Probably the nodes are not being booted correctly thus sshd is not working and thats while the host cant connect

#24

unnivkn:
it may take from vagrant file, once your machine is up…

#25

Bashar:
increased the CPU, destroyed vagrant and starting from scratch

#26

Bashar:
changed the network to 192.168.56.

#27

unnivkn:
ok… check this IP: Ethernet adapter VirtualBox Host-Only Network:

#28

Bashar:
It is 192.168.56.1

#29

unnivkn:
ok… then you are good seems

#30

Bashar:
Which would be the same as the master node?

#31

Bashar:
I can see in Vagrantvile that the master would take 192.168.56.1

#32

Bashar:
Is that ok?

#33

Bashar:
in Ubuntu VM:

boxnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.56.1 netmask 255.255.255.0 broadcast 192.168.56.255

#34

unnivkn:
as per vagrant file it should generate a new IP

#35

unnivkn:
what is the IP for this: enp0s8

#36

unnivkn:
fyi:

image.png
image.png1067×224 12 KB

#37

unnivkn:
https://github.com/hashicorp/vagrant/issues/9834

#38

unnivkn:
https://stackoverflow.com/questions/63043879/vagrant-up-vab-warning-remote-connection-disconnect-retrying

#39

unnivkn:
https://www.thisprogrammingthing.com/2016/fixing-vagrant-connection-error/

#40

unnivkn:
Please go through above links & try again