Updated the documentation about production image usage in README file #10577
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sanjana1604
force-pushed
the
doc/official-docker-image
branch
from
5799d4a to
3a34962
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue: #10363
Updated the Official Docker Images in README.md file. The updated content is mostly done for the users rather than developers of images.
I've added all the points which are necessary to be updated in Official Docker Images section. Link to Airflow Summit 2020's "Production Docker Image" talk is Provided. Explanation of what is Prod image, where it can be used and two options for the image - customization/extension. Link to images in Docker Hub is mentioned and a small point on how to build image using Breeze.
@potiuk any points missing or wrong in Documentation?Please review it and let me know.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.