commit
2bfcf68d07
|
@ -73,7 +73,7 @@ Vagrant generates a private key for each of these VMs. It is placed under the .v
|
|||
|
||||
## Troubleshooting Tips
|
||||
|
||||
If any of the VMs failed to provision, or is not configured correct, delete the vm using the command:
|
||||
1. If any of the VMs failed to provision, or is not configured correct, delete the vm using the command:
|
||||
|
||||
`vagrant destroy <vm>`
|
||||
|
||||
|
@ -97,3 +97,11 @@ In such cases delete the VM, then delete the VM folder and then re-provision
|
|||
`rmdir "<path-to-vm-folder>\kubernetes-ha-worker-2"`
|
||||
|
||||
`vagrant up`
|
||||
|
||||
2. When you try "sysctl net.bridge.bridge-nf-call-iptables=1", it would sometimes return "sysctl: cannot stat /proc/sys/net/bridge/bridge-nf-call-iptables: No such file or directory" error. The below would resolve the issue.
|
||||
|
||||
`modprobe br_netfilter`
|
||||
|
||||
`sysctl -p /etc/sysctl.conf`
|
||||
|
||||
`net.bridge.bridge-nf-call-iptables=1`
|
||||
|
|
Loading…
Reference in New Issue