V0lantis opened a new issue, #37716:
URL: https://github.com/apache/airflow/issues/37716

   ### Apache Airflow version
   
   2.8.1
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   When using custom build, we use the base Airflow Dockerfile. The issue is 
that the first line is `# syntax=docker/dockerfile:1.4`
   
   leading to the following rate limiting in our CI
   
   ```
   Dockerfile:1
   --------------------
      1 | >>> # syntax=docker/dockerfile:1.4
      2 |     # Licensed to the Apache Software Foundation (ASF) under one or 
more
      3 |     # contributor license agreements.  See the NOTICE file 
distributed with
   --------------------
   ERROR: failed to solve: unexpected status from HEAD request to 
https://registry-1.docker.io/v2/docker/dockerfile/manifests/1.4: 429 Too Many 
Requests
   Error: Process completed with exit code 1.
   ```
   
   Is thee anyway this could be mitigated? I tried to use `sed` to replace this 
first line, but this is quite a dirty solution.
   
   ### What you think should happen instead?
   
   _No response_
   
   ### How to reproduce
   
   Hard to reproduce, but I guess, doing thousand of build at the same time 
with the same IP would do the job
   
   ### Operating System
   
   Github Actions on Github Entreprise
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.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]

Reply via email to