Created volume is automatically bound to app [resolved]

Application A has Volume X mounted to it

I created Application B (effectively a staging environment of App A), and I want to create Volume Y to mount to it.

But when I create Volume Y, then try to deploy App B, I get

Error Mounts source volume “[Volume Y]” does not exist

In the web dashboard, it shows Volume Y has been mounted to App A. It’s not clear how or why that is happening.

The volume names are different: deliverables_data and demo_data, respectively.

Sorry I realized the fly volumes command can indeed take a --config parameter. I think I tried fly --config volumes... earlier, and only tried fly volumes --config ... now. This was after I deleted Application A, so fly volumes create complained that the production app (App A) did not exist.