App published to fly.io with volume is losing data after `fly apps restart`

[jayljohnson]

I successfully deployed datasette to fly.io using the command below. I am trying to keep the .db in a persisted volume so that I can add and update data periodically but am running into some problems including:

• After creating a new table, then running fly apps restart, the database is missing the table. Steps to create a new table were:
  • fly ssh console -a some-project
  • apt update && apt install sqlite3
  • sqlite3
  • >.open some.db
  • > .tables
  • some_table
  • > create table test_table as select 1 col1 union select 2;
  • > .tables
  • some_table test_table
• The --install datasette-saved-queries flag doesn't do anything. If I install it locally first before deploying, then it works.
• Created a file with echo some_data > /app/vol1/some_file.txt and it was gone after fly apps restart

Here's the full command I'm using

datasette publish fly data/outputs/sqlite/some.db \
    --app="some-project" \
    --create-volume 2 \
    --volume-name vol1 \
    --static vol1:data/outputs/test/ \
    --install datasette-saved-queries \
    --setting sql_time_limit_ms 25000

I'm not sure if this is a bug or user error, and appreciate any guidance. There's a good chance I'm missing something fundamental about how fly.io volumes work.