Vaultwarden Instance is Giving a Warning Saying There is No Persistent Volume
Hi,
I am trying to set up a vault warden instance, however the deploy logs are giving a warning saying that the lack of persistent volume will lead to data loss on update/restart. I know that railway does not support persistent volumes, so how do I get around this issue? Thanks for the help!
8 Replies
Project ID:
cde47e73-481d-45c6-8392-88e14ad4e960You might find these helpful:
- How to correctly migrate from Heroku to Railway without losing data?
- Help needed in deploying vaultwarden template to railway
- Persist Some Files?
⚠️ experimental feature
I believe the project ID is
cde47e73-481d-45c6-8392-88e14ad4e960Error:
Looks like the error message tells you exactly what to do. Set an environment variable called I_REALLY_WANT_VOLATILE_STORAGE to True
Yeah that is what I did, however I want to make sure I am not going to suffer data loss when the container restarts.
This basically just ignores the warning
Railway does not offer persistent storage. Every time the service restarts your data will be lost
if you're looking for persistent storage, look into other services
Yup, fully aware on that front but thanks for letting me know! If this is the case however, why would railway offer this as a built in template? Doesn't this mean that railway is not a good choice for hosting a vault warden instance?