Feature #11255
Updated by Peter Amstutz about 7 years ago
Docker bridge networking has bugs on certain kernels. Add a flag to crunch-run to instruct containers to use host networking instead of the default bridge network. Intend to support the following use case: the entire cluster is running compute nodes which will use host networking instead of bridge networking. Sysadmin will specify the option via command line (which can be configured in crunch-dispatch-slurm). We will provide two Two options: * Use host networking when networking is enabled, and "none" when it is disabled. When a container is created with --net=none, the container is given an "empty" network namespace (only the loopback device is available.) If kernel bugs are associated with Docker's bridge networking, this option would use host networking for those containers that need it, while maintaining isolation for containers that don't need networking. enabled * Use host networking for all containers. no matter what If kernel bugs make network namespaces totally unusable, always use --net=host, so that network namespaces are not used at all. This should sidestep the issue, at the expense of reduced isolation from the host system.