potiuk opened a new pull request #20987: URL: https://github.com/apache/airflow/pull/20987
Seems that when AUFS is a backing storage for Docker, changing the script to executable and executing it right after during the build phase might cause an error: 'text file busy' https://github.com/moby/moby/issues/13594 Workaround for that is to add extra `sync` command after changing the executable flag to make sure that the filesystem change has propageted to the underlying AUFS storage. This PR adds the sync and also makes sure that both CI And PROD image use same formatting, executable bits and `&&` between commands rather than `;`. The `&&` is better to separate the commands because it will not continue with execution steps in the same bash command after previous command fails. This caused confusion as to what is the reason for docker build failure. The problem was raised in the #20971 discussion. <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
