Shippable / support

Shippable SaaS customers can report issues and feature requests in this repository
100 stars 28 forks source link

Can't download docker image #5115

Open stavros-zavrakas opened 4 years ago

stavros-zavrakas commented 4 years ago

Description of your issue:

NOTE: If you are experiencing a build failure, please include:

Downloading the docker image is taking forever. It was working normally up till yesterday. The docker image can be downloaded normally locally in our computers. Right now it's trying to download the image the last 45 minutes and I have stopped the previous one when it was running for 38 minutes:

build_pre_ci
  docker build -t caenpd/u16pytallnpd:v0.2 ./deployment
Sending build context to Docker daemon  10.24kB

Step 1/6 : FROM drydock/u16pytall:v7.2.4
v7.2.4: Pulling from drydock/u16pytall
7b722c1070cd: Pulling fs layer
5fbf74db61f1: Pulling fs layer
ed41cb72e5c9: Pulling fs layer
7ea47a67709e: Pulling fs layer
2aee0a36a645: Pulling fs layer
ccfe386eab02: Pulling fs layer
33eb24a339c3: Pulling fs layer
40491d776538: Pulling fs layer
3c58753a2be8: Pulling fs layer
c0378f9f23bf: Pulling fs layer
292a9ec0992d: Pulling fs layer
33eb24a339c3: Waiting
40491d776538: Waiting
3c58753a2be8: Waiting
c0378f9f23bf: Waiting
292a9ec0992d: Waiting
2aee0a36a645: Waiting
ccfe386eab02: Waiting
7ea47a67709e: Waiting
5fbf74db61f1: Verifying Checksum
5fbf74db61f1: Download complete
ed41cb72e5c9: Verifying Checksum
ed41cb72e5c9: Download complete
2aee0a36a645: Download complete
7ea47a67709e: Verifying Checksum
7ea47a67709e: Download complete
33eb24a339c3: Verifying Checksum
33eb24a339c3: Download complete
40491d776538: Retrying in 5 seconds
40491d776538: Retrying in 4 seconds
40491d776538: Retrying in 3 seconds
40491d776538: Retrying in 2 seconds
40491d776538: Retrying in 1 second
7b722c1070cd: Retrying in 5 seconds
7b722c1070cd: Retrying in 4 seconds
7b722c1070cd: Retrying in 3 seconds
7b722c1070cd: Retrying in 2 seconds
7b722c1070cd: Retrying in 1 second
7b722c1070cd: Retrying in 10 seconds
7b722c1070cd: Retrying in 9 seconds
7b722c1070cd: Retrying in 8 seconds
7b722c1070cd: Retrying in 7 seconds
7b722c1070cd: Retrying in 6 seconds
7b722c1070cd: Retrying in 5 seconds
7b722c1070cd: Retrying in 4 seconds
7b722c1070cd: Retrying in 3 seconds
7b722c1070cd: Retrying in 2 seconds
7b722c1070cd: Retrying in 1 second
7b722c1070cd: Verifying Checksum
7b722c1070cd: Download complete
3c58753a2be8: Verifying Checksum
3c58753a2be8: Download complete
7b722c1070cd: Pull complete
5fbf74db61f1: Pull complete
ed41cb72e5c9: Pull complete
7ea47a67709e: Pull complete
2aee0a36a645: Pull complete
c0378f9f23bf: Retrying in 5 seconds
c0378f9f23bf: Retrying in 4 seconds
c0378f9f23bf: Retrying in 3 seconds
c0378f9f23bf: Retrying in 2 seconds
FROM drydock/u16pytall:v7.2.4

ADD . /u16pytallnpd

ENV NVM_DIR /root/.nvm
ENV NODE_VERSION 12.14.1
ENV AWS_SAM_VERSION 0.52.0
ENV GLIBC_VER=2.31-r0

RUN /u16pytallnpd/install.sh
a-murphy commented 4 years ago

All three failures to pull were running on the same node and it appears to have succeeded since then, on a different node. It was probably a problem with that particular node, possibly with its network connection. Let us know if you see this again, but it's unlikely to be a common problem.

In the unlikely event that this does happen again, I noticed that you also have a node pool with the v7.2.4 machine image, which would already have the image present on the node and should avoid pulling the image entirely. You can specify the node pool to use in your shippable.yml to use the other node pool instead.