Need help understanding this error message using flyctl

When I run flyctl launch, it ends up with an error and says:

==> Validating app configuration

--> Validating app configuration done


TCP 80/443 ⇢ 8080

Error Post "": read tcp> read: connection reset by peer

Anybody got any idea what this means? flyctl doctor gives all green lights.

Ok, this is odd. When my collegue runs flyctl launch on the same app, they get:

$ fly launch
An existing fly.toml file was found for app catadesk-staging
App is not running, deploy...
Deploying catadesk-staging
==> Validating app configuration
--> Validating app configuration done
TCP 80/443 ⇢ 8080
Error Mounts source volume "vol_" does not exist

I’m not sure about the first error (the connection reset by peer one) however it seems someone else is also getting that volume vol_ one:

Seems to be an issue. Hopefully someone from Fly can check on volumes either here/there as there seems to be something up.

Hi @catadesk your colleagues error message Error Mounts source volume "vol_" does not exist is because they don’t have volumes provisioned for their app. They need to run fly volumes create <volume name> --region ... --size ... and then add [mount] in their fly.toml.

They may find this section in the docs helpful.

This is very odd, because it is a project which is deployed as a new app with no fly.toml nor Dockerfile or the likes existing.

We were under the impression that fly launch would perform all required steps, including setting up a database cluster (which presumably the volume is for), as this was the case in the past, when setting up other apps.

EDIT: It seems like the issues we encounter are the same as, or at least related to, Timeout on - #15 by tomgeene and Deploy errors: Post "": unexpected EOF - #11 by le_simon

What I’m now wondering is whether the mysterious “vol_” (that does not exist) is used by the app, or by the remote builder used to build the app (image) …

To rule out it being the remote builder, do you have Docker running locally? You can check if not sure by using fly doctor e.g

$ fly doctor
Testing authentication token... PASSED
Testing flyctl agent... PASSED
Testing local Docker instance... Nope
Pinging WireGuard gateway (give us a sec)... PASSED

If you do have Docker available, that would avoid the need for a remote builder. If the deploy works, that would suggest the “vol_” error is being caused by the builder. If not, it would suggest it is the app (like one not provisioned).

The potential complication is I see that fly deploy supports a --local-only flag. But fly launch does not (or at least, it’s not documented if it does). Hmm. But I believe if Docker is running locally, that is used, as the default. So if you do have Docker available, that’s worth a shot while Fly investigate further.

fly launch

fly deploy