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/10 01:38:48 UTC

[GitHub] [airflow] budney opened a new pull request #22135: Fixed permissions error in Docker image by adding read permission to entrypoint

budney opened a new pull request #22135:
URL: https://github.com/apache/airflow/pull/22135


   When I build the docker image, Airflow fails to start. The logs show repeated "permission denied" errors. This is caused by the entrypoint script having execute *but not* read permissions. This PR adds read permissions to the entrypoint in the docker image.
   
   Others might not get this error if they have relatively open umask, because in that case read permissions are already present. This makes it explicit.
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information.
   In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md).
   


-- 
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



[GitHub] [airflow] potiuk edited a comment on pull request #22135: Fixed permissions error in Docker image by adding read permission to entrypoint

Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on pull request #22135:
URL: https://github.com/apache/airflow/pull/22135#issuecomment-1063960188


   Ah inded. This might be the case if you have very strict umask. BTW it might also lead to a number of caching problems (as files will have different permission for you than for everyone else. 
   
   Have you considered to set `git config --global core.sharedRepository 0600` to overcome the problem with the default umask of yours ? 
   


-- 
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



[GitHub] [airflow] potiuk edited a comment on pull request #22135: Fixed permissions error in Docker image by adding read permission to entrypoint

Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on pull request #22135:
URL: https://github.com/apache/airflow/pull/22135#issuecomment-1063960188


   Ah inded. This might be the case if you have very strict umask. BTW it might also lead to a number of caching problems (as files will have different permission for you than for everyone else. 
   
   Have you considered to set `git config --global core.sharedRepository 0600` to overcome the problem with the default umask of yours for example ? 


-- 
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



[GitHub] [airflow] potiuk edited a comment on pull request #22135: Fixed permissions error in Docker image by adding read permission to entrypoint

Posted by GitBox <gi...@apache.org>.
potiuk edited a comment on pull request #22135:
URL: https://github.com/apache/airflow/pull/22135#issuecomment-1063960188


   Ah inded. This might be the case if you have very strict umask. BTW it might also lead to a number of caching problems (as files will have different permission for you than for everyone else. 
   
   Have you considered to set `git config --global core.sharedRepository 0600` to overcome that default of yours ? 
   


-- 
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



[GitHub] [airflow] github-actions[bot] commented on pull request #22135: Fixed permissions error in Docker image by adding read permission to entrypoint

Posted by GitBox <gi...@apache.org>.
github-actions[bot] commented on pull request #22135:
URL: https://github.com/apache/airflow/pull/22135#issuecomment-1063960794


   The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease.


-- 
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



[GitHub] [airflow] boring-cyborg[bot] commented on pull request #22135: Fixed permissions error in Docker image by adding read permission to entrypoint

Posted by GitBox <gi...@apache.org>.
boring-cyborg[bot] commented on pull request #22135:
URL: https://github.com/apache/airflow/pull/22135#issuecomment-1064007763


   Awesome work, congrats on your first merged pull request!
   


-- 
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



[GitHub] [airflow] potiuk merged pull request #22135: Fixed permissions error in Docker image by adding read permission to entrypoint

Posted by GitBox <gi...@apache.org>.
potiuk merged pull request #22135:
URL: https://github.com/apache/airflow/pull/22135


   


-- 
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



[GitHub] [airflow] boring-cyborg[bot] commented on pull request #22135: Fixed permissions error in Docker image by adding read permission to entrypoint

Posted by GitBox <gi...@apache.org>.
boring-cyborg[bot] commented on pull request #22135:
URL: https://github.com/apache/airflow/pull/22135#issuecomment-1063565649


   Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
   Here are some useful points:
   - Pay attention to the quality of your code (flake8, mypy and type annotations). Our [pre-commits]( https://github.com/apache/airflow/blob/main/STATIC_CODE_CHECKS.rst#prerequisites-for-pre-commit-hooks) will help you with that.
   - In case of a new feature add useful documentation (in docstrings or in `docs/` directory). Adding a new operator? Check this short [guide](https://github.com/apache/airflow/blob/main/docs/apache-airflow/howto/custom-operator.rst) Consider adding an example DAG that shows how users should use it.
   - Consider using [Breeze environment](https://github.com/apache/airflow/blob/main/BREEZE.rst) for testing locally, itโ€™s a heavy docker but it ships with a working Airflow and a lot of integrations.
   - Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
   - Please follow [ASF Code of Conduct](https://www.apache.org/foundation/policies/conduct) for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
   - Be sure to read the [Airflow Coding style]( https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#coding-style-and-best-practices).
   Apache Airflow is a community-driven project and together we are making it better ๐Ÿš€.
   In case of doubts contact the developers at:
   Mailing List: dev@airflow.apache.org
   Slack: https://s.apache.org/airflow-slack
   


-- 
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



[GitHub] [airflow] potiuk commented on pull request #22135: Fixed permissions error in Docker image by adding read permission to entrypoint

Posted by GitBox <gi...@apache.org>.
potiuk commented on pull request #22135:
URL: https://github.com/apache/airflow/pull/22135#issuecomment-1063960188


   Ah inded. This might be the case if you have very strict umask. BTW it might also lead to a number of caching problems (as files will have different permission for you than for everyone else. 
   
   Have you considered to set `git config --global core.sharedRepository 0002` to overcome that default of yours ? 
   


-- 
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