See #39068
If the docker-py image (which is currently built inside the test container, so docker-in-docker), DNS resolution fails in the build:
14:40:56 W: Failed to fetch http://deb.debian.org/debian/dists/jessie/InRelease
14:40:56
14:40:56 W: Failed to fetch http://security.debian.org/debian-security/dists/jessie/updates/InRelease
14:40:56
14:40:56 W: Failed to fetch http://deb.debian.org/debian/dists/jessie/Release.gpg Temporary failure resolving 'deb.debian.org'
14:40:56
14:40:56 W: Failed to fetch http://security.debian.org/debian-security/dists/jessie/updates/Release.gpg Temporary failure resolving 'security.debian.org'
14:40:56
14:40:56 W: Some index files failed to download. They have been ignored, or old ones used instead.
Changing the order in which tests are run (6aafe0f) makes the test pass.
We need to investigate what causes this to fail; if the test-integration/test-integration-cli makes modifications to networking that causes this behavior
See #39068
If the docker-py image (which is currently built inside the test container, so docker-in-docker), DNS resolution fails in the build:
Changing the order in which tests are run (6aafe0f) makes the test pass.
We need to investigate what causes this to fail; if the test-integration/test-integration-cli makes modifications to networking that causes this behavior