Volumes "safe mode"?

It would be great to be able to have a “safe mode” to access fly volumes. Basically a shell to be able to access the filesystem.

For a recent deployment, I had a bug where my machine wouldn’t start due to bad data on disk. I would have liked to be able to delete or repair the bad data, but I didn’t have the ability to access the volume since the machine wouldn’t even start.

It would be great to be able to, if the machine is offline, still have a way to access the underlying volume. In my case, I had to delete the machine, and then delete the entire volume (since spinning up a new machine would have still failed due to corrupt data), and then recreate both.

I could update my app to not terminate the process if the underlying data is bad. But I’d rather not do that - if the storage is bad I want to terminate the process. On a regular VM (or on localhost) I’d be able to just SSH in, fix data, and restart the process and I’d love to be able to have an equivalent here!

A command like the following will do what you want:

fly machine run --shell --region yul --volume vol_vd3ykk9km950kdwr:/data

Notes:

  • Generally you will need to specify a region, otherwise you can get a “wrong region” error if your closest region doesn’t match
  • The default image is ubuntu. You can specify a different image if you prefer using --image.
1 Like

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