Error: creating a new machine in group 'app' requires an unattached 'data' volume. Create it with `fly volume create data`

[andie]

There’s definitely a few things going on here. Your app may not have fully migrated to V2; your platform should be Machines. So, you can try this solution first:

Livebook app is suspended after upgraded to v2 machine

Your app seems to be in a “detached” state - this is a sort of halfway-migrated state that should only happen while an app is being migrated. Fixing this shouldn’t be that bad. You should be able to run fly resume <appname> # to get out of the "suspended" state fly scale count 0 -a <appname> # to kill any leftover VMs from the old platform, if there are any # scale count 0 might take a minute to propagate in the backend. # if the next command fails, try it again after a few seconds. fly apps s…

Edit to add: try deploying at this point and if the volume error persists, try the steps below

Then for the volume issue. I’d need to see the exact fly deploy command and the complete output, but my guess is that this is because of the Apps V2 HA feature that creates 2 Machines by default for process groups with services.

You could try creating a second volume, also called data, and then running fly deploy again. Alternatively use the --ha option in fly deploy to turn off the “create 2 machines” feature:
fly deploy --ha=false