You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/03/15 17:51:04 UTC

[GitHub] [airflow] potiuk edited a comment on pull request #22292: Fail with error when extending image with pip run as root

potiuk edited a comment on pull request #22292:
URL: https://github.com/apache/airflow/pull/22292#issuecomment-1068278745


   > This makes me think maybe pip should gain a flag that disables root invocation altogether, e.g. `pip --no-root` would refuse to do anything instead of warn if the uid is 0.
   
   Yeah. Why not. As long as we can control it somehow. I do think rather than "policing" (and producing the warning) giving control to the users who are using `pip` as part of the pipeline is much better idea (but - as discussed for a long time, those power users of `pip` who have their own users should be able to control it).
   
   The funny thing in this case that users are so used to the `root` warning that it did absolutely nothing to prevent the user to make the mistake. The user saw the "do not use pip as root` as warning but happily ignored it, and it require a slack conversation and close looking at the Dockerfile of the user to help him.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org