Hi everyone,
Of the following, all work except for bom.
I executed the following commands in the presented sequence:
❯ fly vol create repos -n 1 -r “cdg” --snapshot-retention 1
Result: Works
❯ fly vol create repos -n 1 -r “bom” --snapshot-retention 1
Error: failed to create volume: app is already using all available zones in region bom (Request ID: 01K2M9WT2FFR4TEZFG8E2A6X12-cdg)
❯ fly vol create repos -n 1 -r “den” --snapshot-retention 1
Result: Works
Please help. Thank you.
This is the source of the problem, I bet. By default, fly vol create puts volumes on separate physical machines,† and you ran out of those in bom (which is generally one of the smaller regions, as I understand it).
You can opt-out with --require-unique-zone=false, I think, but be aware that this gives you worse reliability in case of hardware failure, etc.
You might prefer to shift some to Singapore, or the like.
Hope this helps a little!
†This is probably over-simplifying, but it gives the right general idea.
@mayailurus Thank you for your help! Unfortunately, no dice:
❯ fly vol create repos -n 1 --snapshot-retention 1 --require-unique-zone=false
Select region: Mumbai, India (bom)
Error: failed to create volume: no capacity available in bom (Request ID: 01K2MB3C1CX7BVV2Z1N0H68ZKY-cdg)
And I can’t switch from bom due to having already paid the whole year in advance for a machine in that specific region. This is a bit of a letdown since I’m only trying to provision single a 1GB volume — nothing crazy.
Hm… You can try waiting it out to see whether something becomes available later today / this week. Once the workweek winds down, there might be more space free. (Anecdotally, a lot of builders seem to get created there—even for people in Australia(?), sometimes.)
Alternatively, it might be worth emailing billing@fly.io to ask if you can get the reservation shifted to a larger region. I don’t know whether that definitely works in this case, but it seems reasonable to inquire…
@mayailurus Thank you, I’ve emailed billing@fly.io.