The entrypoints in Docker Image should be owned by Airflow #10853
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
Since we are running the airflow image as airflow user, the entrypoint and clear-logs scripts should also be set as airflow. This had no impact if you actually run this as root user or when your group was root (which was recommended).
mik-laj
approved these changes
Sep 10, 2020
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
Sep 14, 2020
) Since we are running the airflow image as airflow user, the entrypoint and clear-logs scripts should also be set as airflow. This had no impact if you actually run this as root user or when your group was root (which was recommended). (cherry picked from commit d9920fa)
potiuk
added a commit
that referenced
this pull request
Sep 15, 2020
Since we are running the airflow image as airflow user, the entrypoint and clear-logs scripts should also be set as airflow. This had no impact if you actually run this as root user or when your group was root (which was recommended). (cherry picked from commit d9920fa)
RaviTezu
pushed a commit
to RaviTezu/airflow
that referenced
this pull request
Oct 25, 2020
) Since we are running the airflow image as airflow user, the entrypoint and clear-logs scripts should also be set as airflow. This had no impact if you actually run this as root user or when your group was root (which was recommended). (cherry picked from commit d9920fa)
kaxil
pushed a commit
that referenced
this pull request
Nov 12, 2020
Since we are running the airflow image as airflow user, the entrypoint and clear-logs scripts should also be set as airflow. This had no impact if you actually run this as root user or when your group was root (which was recommended). (cherry picked from commit d9920fa)
potiuk
added a commit
that referenced
this pull request
Nov 16, 2020
Since we are running the airflow image as airflow user, the entrypoint and clear-logs scripts should also be set as airflow. This had no impact if you actually run this as root user or when your group was root (which was recommended). (cherry picked from commit d9920fa)
cfei18
pushed a commit
to cfei18/incubator-airflow
that referenced
this pull request
Mar 5, 2021
) Since we are running the airflow image as airflow user, the entrypoint and clear-logs scripts should also be set as airflow. This had no impact if you actually run this as root user or when your group was root (which was recommended). (cherry picked from commit d9920fa)
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.
Since we are running the airflow image as airflow user, the
entrypoint and clear-logs scripts should also be set as airflow.
This had no impact if you actually run this as root user or
when your group was root (which was recommended).
^ 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.