lupyuen commented on issue #14376:
URL: https://github.com/apache/nuttx/issues/14376#issuecomment-2439840659

   Something strange about __Network Timeouts__ in our Docker Workflows: First 
Run fails while [downloading something from 
GitHub](https://github.com/nuttxpr/nuttx/actions/runs/11535899222/job/32111488205#step:7:626):
   ```text
   Configuration/Tool: imxrt1050-evk/libcxxtest,CONFIG_ARM_TOOLCHAIN_GNU_EABI
   curl: (28) Failed to connect to github.com port 443 after 134188 ms: 
Connection timed out
   make[1]: *** [libcxx.defs:28: libcxx-17.0.6.src.tar.xz] Error 28
   ```
   
   Second Run fails again, while [downloading NimBLE from 
GitHub](https://github.com/nuttxpr/nuttx/actions/runs/11535899222/job/32112716849#step:7:536):
   ```text
   Configuration/Tool: nucleo-wb55rg/nimble,CONFIG_ARM_TOOLCHAIN_GNU_EABI
   curl: (28) Failed to connect to github.com port 
[443](https://github.com/nuttxpr/nuttx/actions/runs/11535899222/job/32112716849#step:7:444)
 after 134619 ms: Connection timed out
   make[2]: *** [Makefile:55: 
/github/workspace/sources/apps/wireless/bluetooth/nimble_context] Error 2
   ```
   
   [Third Run 
succeeds.](https://github.com/nuttxpr/nuttx/actions/runs/11535899222) Why do we 
keep seeing these errors: GitHub Actions with Docker, can't connect to GitHub 
itself?
   
   Is something misconfigured in our Docker Image? But the exact same Docker 
Image runs fine on [my own Build 
Farm](https://lupyuen.codeberg.page/articles/ci2.html). It [doesn't show any 
errors](https://lupyuen.codeberg.page/articles/ci2.html).
   
   Is GitHub Actions starting our Docker Container with the wrong MTU (Network 
Packet Size)? 🤔
   - https://github.com/actions/actions-runner-controller/issues/393
   - [Docker MTU issues and solutions](https://mlohr.com/docker-mtu/)


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