Since those are simply snapshots of the existing python images, DockerHub does not create a separateĬopy of those images - all layers are mounted from the original python images and those are merely To airflow repository, we also push the python image that was used to build it this image is stored Last week might be a different image than python3.8 today. Python images are regularly updated (with bugfixes/security fixes), so for example python3.8 from Each CI image, when built uses current python version of the base images. We also store (to increase speed of local build/pulls) python images that were used to build * The ``-manifest`` is added for manifest images (see below for explanation of manifest images) * The ``-ci`` suffix is added for CI images * ``PYTHON_MAJOR_MINOR_VERSION`` - version of python used to build the image. The ``1.10.*`` and ``2.*`` labels are built from git tags The ``master``, ``v1-10-test`` ``v2-0-test`` labels areīuilt from branches so they change over time. * ``BRANCH_OR_TAG`` - branch or tag used when creating the image. * CI image (Dockerfile.ci) - used for running tests and local development. You can read more about building and using the production image in the * Production image (Dockerfile) - that can be used to build your own production-ready Airflow installation Specific language governing permissions and limitationsĪirflow has two images (build from Dockerfiles): "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY Software distributed under the License is distributed on an Unless required by applicable law or agreed to in writing, "License") you may not use this file except in compliance To you under the Apache License, Version 2.0 (the See the NOTICE fileĭistributed with this work for additional information
AIRFLOW GITHUB EXAMPLES SOFTWARE
Licensed to the Apache Software Foundation (ASF) under one
0 kommentar(er)
