Error Joining the Worker Node - k8sSecond.sh

katsloko

Does anyone encountered this error before and what would be the possible fix?
For some reason, I cannot join the Control Plane from Worker Node after setup.

vagrant@vagrant:~$ sudo kubeadm join 10.0.2.x:6443 --token x4zydl.f03w85c7pookbejw --discovery-token-ca-cert-hash sha256:e54d422ceab89dae3232f4195798702a3227a82be6c2b52110aac8787098aaf
 
[preflight] Running pre-flight checks
error execution phase preflight: [preflight] Some fatal errors occurred:
        **[ERROR FileContent--proc-sys-net-bridge-bridge-nf-call-iptables]: /proc/sys/net/bridge/bridge-nf-call-iptables does not exist**
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher
vagrant@vagrant:~$ Thank you for your help.

My VirtualBox:
Base Memory: 8192MB
Processor: 4
Image: hashicorp/bionic64
Completed: swapoff -a and commented the /etc/fstab setting.

chrispokorni

Hi @katsloko,

When running labs on VirtualBox VMs the networking configuration of the VM instances plays the most important role in the successful bootstrapping of the cluster. I would recommend a single bridged adapter per VM to avoid other set up headaches.

Please watch the GCE and/or AWS EC2 instances provisioning videos from the first chapter, for tips on how to configure the networking of the two VM instances of the lab environment.

Regards,
-Chris