Preview: Deploying applications on Machines with flyctl

flyctl m clone is either defunct or broken: flyctl machine clone is defunct?

There’s a bunch of nil pointer dereference in code because of the differences between regular Fly apps and Machine apps. I’ve seen this to be the cause of such error msgs.

If you want to, you can git clone flyctl, build it locally with go build -o fly2 and use that. fly2 should now show panics and stacktraces, unlike the prod version.

Yikes. Do report it here: Issues · superfly/flyctl · GitHub

1 Like