From cff2dbec74b9f040910bd8a39091bdb9621017be Mon Sep 17 00:00:00 2001 From: Thileepan Sivanantham <41337294+thilees@users.noreply.github.com> Date: Sun, 14 Jun 2020 07:49:51 +0530 Subject: [PATCH] Update 02-compute-resources.md Fix the issue returns by "sysctl net.bridge.bridge-nf-call-iptables=1" in latest ubuntu versions and number the tips --- docs/02-compute-resources.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/02-compute-resources.md b/docs/02-compute-resources.md index a06c070..852e03d 100644 --- a/docs/02-compute-resources.md +++ b/docs/02-compute-resources.md @@ -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 ` @@ -97,3 +97,11 @@ In such cases delete the VM, then delete the VM folder and then re-provision `rmdir "\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`