New fly.toml [mount] directive disassociates my machine from my volume

Questions / Help
,
1

Hey y’all,
I had some machines running with volumes attached. Volumes persisted data, machines accessed and delivered the data.

As my machines occasionally, naturally, restart (since they are ephemeral images that come and go like a gentle summer zephyr) they restart and look for the [mounts] directive. My deployments are almost a year old, and so have no [mounts] directive. The machine spin up, dont mount the volume, and have no access to the data. Not ideal!

If I add a [mounts] dirctive to my fly.toml and redeploy, I can attach the volume to machine. Neat. My app had been storing all it’s data in the /data directory. If I use a directive like:

[[mounts]]
  source = 'data'
  destination = './data'

I still can’t see any of my historical data. Where is my old data on the volume, and how should I properly mount it for my app to access now?

A very frustrating what feels like major breaking change to flyctl.

4

How did you get persisted volume before w/o the mount?

5

Great question. I absolutely do not remember.

6

When I mount it to a new path, I can use ssh sftp console to get in there and poke around. But there’s absolutely not 178mb of data. Strange!

7

I’d suggest posting the outputs of fly vol list and fly m list at this point, since it’s not clear to me, at least, what the overall menagerie is…

(We forum readers can’t access your app settings, etc.)

9

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.