Quick start docker-compose.yaml file uses an invalid tag
See original GitHub issueApache Airflow version: 2.0.1
Environment:
- OS (e.g. from /etc/os-release): macOS 11.1
- Kernel (e.g.
uname -a
): Darwin Kernel Version 20.2.0 - Install tools: docker-compose
What happened:
Following the steps in the Quick start > Running Airflow in Docker page, I pulled down the pre-made docker-compose.yaml file (https://airflow.apache.org/docs/apache-airflow/2.0.1/docker-compose.yaml) and ran docker-compose up airflow-init
within the same directory as the docker-compose file. This command failed with: Pulling airflow-init (apache/airflow:2.0.1)... ERROR: manifest for apache/airflow:2.0.1 not found: manifest unknown: manifest unknown
.
What you expected to happen: The latest stable official airflow docker image to be pulled, and airflow-init to complete successfully.
How to reproduce it:
Follow the instructions per the quick start docs (https://airflow.apache.org/docs/apache-airflow/stable/start/docker.html) to pull down the docker-compose.yaml file, then attempt to run docker-compose up airflow-init
.
Anything else we need to know: After seeing this I took a look on dockerhub and it does not appear there is a ‘2.0.1’ tagged image. I then tried simply altering the docker-compose file to instead use the latest tag (with no other changes), which pulled successfully, but did not initialize successfully. I ended up using a different pre-made docker-compose file altogether which used a valid 2.0.1 tag.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (4 by maintainers)
Top GitHub Comments
To be clear to anyone else finding this, I had to replace this line in the quickstart docker compose:
image: ${AIRFLOW_IMAGE_NAME:-apache/airflow:2.0.1}
with this line:image: ${AIRFLOW_IMAGE_NAME:-apache/airflow:2.0.1-python3.8}
and rundocker-compose up airflow-init
again.and
apache/airflow:latest
should work too