Open sfc-gh-cbaechtold opened 2 years ago
Had a customer encounter this Monday as well.
https://github.com/astronomer/ap-airflow/blob/05568b66dee3c183441afc589174a848fcd8808e/2.2.5/bullseye/Dockerfile#L113. <- the version pinned here doesn't appear to be released yet per ticket 9180 on zendesk.
Is there any way to roll back via argument when running the docker build
command? e.g. I have the previous image already built locally so can run no problem, but for lab participants, is there a way that they can run the docker build
for the first time and rollback to the previously working version until the pinned version is released?
Current workaround is to pass VERSION=2.2.5-2
in as a build-arg, this works:
DOCKER_BUILDKIT=0 docker build --build-arg PYTHON_MAJOR_MINOR_VERSION=3.8 --build-arg VERSION=2.2.5-2 -t ap-airflow:py38 https://github.com/astronomer/ap-airflow.git#master:2.2.5/bullseye
A similar problem exists in 2.3.3. The issue is line
asks Docker to install astronomer_certified
at version 2.3.3-2-*
, but no such version exists: (https://pip.astronomer.io/simple/astronomer-certified/). The solution above fixes it by passing --build-arg VERSION=2.3.3.*
to docker build
.
I am no longer able to build the latest Airflow image on Docker for Desktop version 4.6.1 (76265), running Mac OS Monterey v12.3.1.
I previously had been able to successfully build the 2.2.5 release, but that now fails. I also tried building the 2.3.0 release, and that also failed. Both due to pip being unable to find a version that satisfied requirements for astronomer-certified[.....]==2.2.5-3-* (and 2.3.0 similarly). Full stack trace: