Github Actions require a lot of network setup to use our builders. What you’re seeing is times when it’s slow to create a wireguard peer (flyctl needs a wireguard peer if it has never connected before). Since each github action run is a new flyctl instance, it needs to create a new peer.
That error looks like a race creating new peers, which is an interesting problem that I haven’t seen before. I’m guessing multiple simultaneous gh actions runs are the cause.
The best way to use GitHub actions is actually to use their Docker daemon + Docker caching. They make this hard to setup, but it will work very well for what you’re doing. Here’s an example of how to configure it: indie-stack/deploy.yml at main · remix-run/indie-stack · GitHub