Build error: cannot apply host to transport: *otelhttp.Transport

Questions / Help Build debugging
1

I’m getting the following error on fly deploy


==> Verifying app config
Validating /Users/ekr/dev/subscribe-gw/.claude/worktrees/resend/fly.toml
✓ Configuration is valid
 → Verified app config
==> Building image
Remote builder fly-builder-frosty-forest-2820 ready
==> Building image
✓ compatible remote builder found
INFO Override builder host with: https://fly-builder-frosty-forest-2820.fly.dev (was tcp://[fdaa:0:d562:a7b:4ec:feda:fc13:2]:2375)

Remote builder fly-builder-frosty-forest-2820 ready
Error: failed to fetch an image or build from source: cannot apply host to transport: *otelhttp.Transport

I have tried fly doctor (everything OK), deleting the builder, and resetting wireguard with no luck.

2

Have you tried not using Depot? There is a switch for it in flyctl.

3

We’re seeing the same issue via both github actions using flyctl and locally using v0.4.33 (there seems to have been an otel dependency upgrade in v0.4.33). This fails for us using depot or the fly builder. Local or remote.

Reverting back to v0.4.32 works fine though. So I’d say a regression from the dependency upgrade

4

Yes, it still fails, but in a different way.

==> Verifying app config
Validating /Users/ekr/dev/subscribe-gw/.claude/worktrees/resend/fly.toml
✓ Configuration is valid
→ Verified app config
==> Building image
Remote builder fly-builder-frosty-forest-2820 ready
Remote builder fly-builder-frosty-forest-2820 ready
==> Building image
✓ compatible remote builder found
INFO Override builder host with: https://fly-builder-frosty-forest-2820.fly.dev (was tcp://[fdaa:0:d562:a7b:4ec:feda:fc13:2]:2375)

Remote builder fly-builder-frosty-forest-2820 ready
WARN Failed to start remote builder heartbeat: failed to parse daemon host “unix:///var/run/docker.sock”: missing hostname

Error: failed to fetch an image or build from source: failed to parse daemon host “unix:///var/run/docker.sock”: missing hostname

5

@ekr: I don’t have a view on what’s happening here, but @byronwilliams’s steer is most helpful. Could you confirm what version of flyctl you’re on, and if you’re on the version that failed for Byron, could you downgrade to see if that helps? If anything, it would be good to rule that out.