[Docker] Pods' IP not in $POD_NETWORK range

[JWimsingues]

When deploying a cluster, everything works well but when I run a few docker's containers on it, pods do not have the appropriate network configuration.

After some troubleshooting, it seems that the range set in the Docker's network is not well configured. The Flannel interface was different from the Docker one.

Finally, the docker.service do not have the --bip option set. It seems that this file (on workers) might be the problem: /etc/systemd/system/docker.service.d/40-flannel.conf. I changed the systemd drop-in in my worker from: EnvironmentFile=/etc/kubernetes/cni/docker_opts_cni.env to: EnvironmentFile=/run/flannel/flannel_docker_opts.env.

After reloading, my pods get the configured sub network specified in etcd.

Am I doing something wrong or is it a problem in the documentation?

I can run a few more tests if required.

[dannymk]

Thank you, I have been banging my head against this issue for about a week. Finally found this and ALL network issues are resolved. The documentation should be updated.

[JWimsingues]

Happy to read that it helps!

[andrewwebber]

@JWimsingues should we create a merge request?
Thanks again for this live saving change :)