Error on Quay.io Image Pulls: `Error response from daemon: `received unexpected HTTP status: 502 Bad Gateway`

Astronomer
1

Issue

Today, the Astronomer Team was alerted of a Quay.io outage beginning at 2021-03-22T13:18-0700. Quay.io is Astronomer’s preferred Docker Registry and hosts both our Airflow docker images as well as all images necessary to run the Astronomer Enterprise platform.

Screen Shot 2021-03-22 at 1.36.29 PM
Screen Shot 2021-03-22 at 1.36.29 PM1686×2236 282 KB

Impact

If you’re pulling an Astronomer Certified image (e.g. FROM quay.io/astronomer/ap-airflow:2.0.0-buster-onbuild) in your Dockerfile, you’ll see a series of errors when you run $ astro deploy. Those errors might look like the following:

Error response from daemon: received unexpected HTTP status: 502 Bad Gateway
docker pull quay.io/astronomer/ap-postgres-exporter:3.13.2
Error response from daemon: received unexpected HTTP status: 502 Bad Gateway
docker pull quay.io/astronomer/ap-prisma:1.34.8
Error response from daemon: received unexpected HTTP status: 502 Bad Gateway
docker pull quay.io/astronomer/ap-prometheus:2.21.0
Error response from daemon: received unexpected HTTP status: 502 Bad Gateway

Users both developing locally via the Astronomer CLI and deploying to Astronomer can expect this error when pulling any ap-airflow image hosted on Quay.io, all of which specify quay.io in their path.

Note: If you’re running Astronomer Enterprise and deploying Astronomer platform images hosted on Quay.io (e.g. ap-fluentd, ap-houston-api, etc.), you’ll run into this issue as well.

Fix

Hang tight for now while Quay.io mitigates the issue. To track updates, refer to:

Note: If you’re pulling images from Astronomer on Docker Hub (e.g. astronomerinc/ap-airflow:2.0.1-buster-onbuild), then you should not experience this problem.