potiuk opened a new pull request #17883: URL: https://github.com/apache/airflow/pull/17883
We need to set the "experimental" flag in CI in order to use `docker manifest` command to check for presence of the images in ghcr.io. In order to use them we need to enable experimental features via ~/.docker/config.json. Sometimes, very rarely we had the case that the config file got broken and the problem turned out to be that we tried to do this experimental replacement in parallel by several running "wait image" commands (:facepalm: here for myself) that were apparenlty overriding the same config.json at the same time in non-atomic way, which (very rarely) led to corrupted file. This change moves the experimental replacement to top-level scripts which are never run in parallel. <!-- 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]
