{subsection: Running ctest in a docker container}
-When running the condor tests inside a docker container, the container must be started with special flags for some of the tests to work. While we hope to fix the tests in the future, for now, starting with
+When running the condor tests inside a docker container, the container must be started with special flags for some of the tests to work. While we hope to fix the tests in the future, for now, starting with a hostname like so
{code}
-docker run --network host --hostname docker.cs.wisc.edu <rest of arguments>
+docker run --hostname docker.cs.wisc.edu <rest of arguments>
{endcode}
-is needed. The unit_test_sinful looks for ipv6 addresses, which most docker containers do not fully support, and running with host networking fixes that problem. Many other tests assume that hostnames are FQDNs, and will fail if the hostname of the container has no dots in it.
+is needed. This is because many tests assume the hostname are FQDNs, and there will be many test timeouts and failures if the hostname of the container has no dots in it. Note that
+
+1: specifying a "--hostname" flag in Docker is NOT compatible with using "--network host", thus it is recommended to use the default NAT networking.
+1: using the default NAT networking also has the nice property of making another virtual interface.... because running the test suite can consume 5k ephemeral network ports, creating a virtual network interface will help prevent the bare metal server from running out of ports.
+1: the unit_test_sinful looks for ipv6 addresses, which most docker containers do not fully support with NAT networking, and thus running in Docker with NAT networking will cause this test to be skipped.
