Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
unversioned
-
None
Description
So this happened while testing other flakiness issues in docker containers:
Step 1/3 : FROM ubuntu:16.04 16.04: Pulling from library/ubuntu 3386e6af03b0: Pulling fs layer 49ac0bbe6c8e: Pulling fs layer d1983a67e104: Pulling fs layer 1a0f3a523f04: Pulling fs layer 1a0f3a523f04: Waiting error pulling image configuration: Get https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/c6/c6a43cd4801e1cf8832aa1dcda0df1f3730eea7e805be27b24cff32b007a919e/data?verify=1576781634-inxZvMHJ5F3MLn3jRt4%2FwWJErSY%3D: dial tcp: lookup production.cloudflare.docker.com on 10.225.0.5:53: read udp 10.225.134.75:52134->10.225.0.5:53: i/o timeout
"docker build" command pulls from external registry, and apparently if that registry is unresponsive, then our builds fail.
We can cache the two images we need (ubuntu:16.04 and ubuntu:18.04) as tarballs and feed them to "docker build", according to this technique. On my machine:
# docker pull ubuntu:16.04 # docker save -o ubuntu:18.04.tar ubuntu:18.04
Save the tarball somewhere, and then on the build host:
# docker load -i ubuntu:18.04.tar
Attachments
Issue Links
- relates to
-
QTQAINFRA-2815 Create local docker mirror
-
- Closed
-