- Newest
- Most votes
- Most comments
The GDAL package is not within scope of what Airflow was intended to do, so the package is not suggested to be installed. Airflow is meant for orchestration, ETL/Geo-spatial libraries require computation and resources that are simply not available on the worker containers.
With that, there are various reasons that it could be failing, including dependency conflicts with other core packages used by Airflow. If you review the constraints line you are using in your PIP installation, you can see that the package is not listed at all, and on libraries.io, it also doesn't list its dependencies which makes troubleshooting it even harder.
It could also be that according to the GDAL website, there is currently only a working binary for Debian based Linux distros, and MWAA containers utilize Amazon Linux (which is a RedHat variant).
Relevant content
- asked 3 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 5 months ago