Closed what5150 closed 3 days ago
Just verifying this is also happening on Github-hosted runners, not just self-hosted. Able to reproduce with standard runner size, ubuntu-latest image. Workaround above works.
This is likely an upstream issue in actions/runner.
@what5150 @ndguarino Can you create a bug report please to help us figure out what's going on?
@crazy-max Will do.
@what5150 Thanks! If you can just post a link of your repo where this issue occurs that would be great as well!
@crazy-max I can't link the repo; org policy, but I did add workflow and build log.
Let's tracked this in #379
Starting 2024-11-08, my build-push-action@v6 steps started failing with exit status 128 and a fatal error "Could not resolve host: yyy.xxxx.com". The only way I could get DNS working again in the build and push step was to add "driver-opts: network=host" to the setup-buildx-action@v3 steps. There haven't been any infrastructure changes, no changes to the runner or its host, the workflow hasn't been edited in months. The runner is on docker, so I spun up another runner on bare metal just to test and had the same issue. Not sure what would cause this.