This may be due to some Quay system issues at the moment: http://status.quay.io/ <http://status.quay.io/>
> On Jul 26, 2017, at 12:39 PM, Dhawal Patel <[email protected]> wrote: > > quay.io/nordstrom/awscli:1.11.30-1 > <http://quay.io/nordstrom/awscli:1.11.30-1> is a public image > > On Wednesday, July 26, 2017 at 12:38:35 PM UTC-7, Dhawal Patel wrote: > docker run --rm \ > > > --net=host \ > > > --user=root \ > > > --volume /opt/bin/:/opt/bin:rw \ > > > quay.io/nordstrom/awscli:1.11.30-1 > > <http://quay.io/nordstrom/awscli:1.11.30-1> aws s3 cp --recursive > > s3://my-bucket/ /opt/bin/ --exclude "*" --include "*.sh" > > Unable to find image 'quay.io/nordstrom/awscli:1.11.30-1 > <http://quay.io/nordstrom/awscli:1.11.30-1>' locally > > /run/torcx/bin/docker: Error response from daemon: Get > https://quay.io/v2/nordstrom/awscli/manifests/1.11.30-1 > <https://quay.io/v2/nordstrom/awscli/manifests/1.11.30-1>: Get > https://quay.io/v2/auth?scope=repository%3Anordstrom%2Fawscli%3Apull&service=quay.io > > <https://quay.io/v2/auth?scope=repository%3Anordstrom%2Fawscli%3Apull&service=quay.io>: > net/http: request canceled (Client.Timeout exceeded while awaiting headers). > > See '/run/torcx/bin/docker run --help'. >
