e7dc964619
The production image had the capability of installing images from wheels (for security teams/air-gaped systems). This capability might also be useful when building CI image espeically when we are installing separately core and providers packages and we do not yet have provider packages available in PyPI. This is an intermediate step to implement #11490 |
||
|---|---|---|
| .. | ||
| README.md | ||
README.md
This folder is par of the Docker context.
Most of other folders in Airflow are not part of the context in order to make the context smaller.
The Production Dockerfile and the CI one Dockerfile.ci copies
the docker-context-files folder to the image context - in case of production image it copies it to
the build segment, co content of the folder is available in the /docker-context-file folder inside
the build image. You can store constraint files and wheel
packages there that you want to install as PYPI packages and refer to those packages using
--constraint-location flag for constraints or by using --add-local-pip-wheels flag.
By default, the content of this folder is .gitignored so that any binaries and files you put here are only used for local builds and not committed to the repository.