I seem to have broken my ability to deploy a new app. Whenever I tried, it goes from
Waiting for remote builder fly-builder-summer-dawn-8254… connecting ⣟
Error error connecting to docker: unable to connect WireGuard tunnel: context deadline exceeded
When I check the status it says pending for the app and when I list apps, pending for the fly-builder as well. I destroyed my existing fly-builder and tried again, but it hasn’t made a difference. I thought something in my environment was causing a timeout, but I just tried to deploy the hellostatic-builtin example and that failed in the same way.
I was able to deploy an app last week! Please let me know what I need to tear down in order to get things moving and shaking again.
Updated to 0.0.241, still getting this problem. I tried flyctl 0.0.238, which is the last time it worked, but the waiting for remote builder still timed out. I’m trying to nail down if it is a problem in my environment and if so, where.
I’m going to try another machine from within my network and see if that makes a difference.
FYI, this is happening for me also as of today. To confirm, I am deploying using a Github action. However I’ve been doing this with all my private and commercial apps, and it has been working fine. I’ll take a look at building the container on GH’s side, but I’m wondering whether there’s a way to increase the timeout?
@OldhamMade If by this you are only getting a timeout (rather than e.g “error during connect” or “EOF” or one of the other issues/errors mention in this thread) the good news is thatone may be fixed as soon as tomorrow, based on this post. It’s because of the time taken for the peer.
Until then the solution I found was to persist the config.yml file between deploys (you may see the fly deploy command complain about it missing if not). As with CI, generally that file is not persisted, resulting in a big delay. Not sure how you do that with Github Actions specifically though.