context deadline exceeded

[gerhard-pretorius]

How I deal with this?

✓ Configuration is valid
→ Verified app config
==> Building image
Remote builder fly-builder-bold-rain-564 ready
Error: failed to fetch an image or build from source: Get “http://fdaa:8:5732:a7b:1cf:6be3:5b82:2:8080/flyio/v1/extendDeadline”: context deadline exceeded
Stacktrace:
goroutine 1 [running]:
runtime/debug.Stack()
runtime/debug/stack.go:24 +0x64
github.com/superfly/flyctl/internal/cli.printError(0x140004ffea0, 0x1400098fc06, 0x1400070c908, {0x1029ff2c8, 0x140002f0720})
github.com/superfly/flyctl/internal/cli/cli.go:184 +0x458
github.com/superfly/flyctl/internal/cli.Run({0x102a1c700?, 0x14000b9ab80?}, 0x140004ffea0, {0x14000118400, 0x2, 0x2})
github.com/superfly/flyctl/internal/cli/cli.go:109 +0x758
main.run()
github.com/superfly/flyctl/main.go:47 +0x174
main.main()
github.com/superfly/flyctl/main.go:26 +0x20

[lubien]

Hi @gerhard-pretorius

We added a flag that might help with that, can you give it a try?

Performing remote builds without wireguard

Context Remote builds for deployments are conducted by your free-builder over a wireguard tunnel, by default. But sometimes, connectivity between flyctl and your builder breaks down due to communication issues over wireguard and this prevents you from deploying your apps. The most common way this manifests itself is through an uptick in remote builder heartbeart errors. To remedy this situation, we’ve added a flag that allows you to perform deployments without wireguard. Usage fly deploy --wg…

Also spoiler: we’ve been working on making this automatically failover to that flag, there’s a Fresh Produce incoming