-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a persistent volume check. #2501
Add a persistent volume check. #2501
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not convinced reading the diff on how it does work, can you explain a bit more ?
Within the container it creates a special file. This special file is checked within the code. If this file exists then Vaultwarden will exit. That file should disappear if docker mounts over the data folder, and hence that file should be gone. |
Aha ! |
7390053
to
f944be0
Compare
Done :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perfect, missing Dockerfile updates from template but okay :)
Meh forgot to run make. Will do that later |
This will add a persistent volume check to make sure when running containers someone is using a volume for persistent storage. This check can be bypassed if someone configures `I_REALLY_WANT_VOLATILE_STORAGE=true` as an environment variable. This should prevent issues like dani-garcia#2493 .
f944be0
to
40ed505
Compare
It seemed there were some issues building the cross-platform images. This PR fixes dani-garcia#2501 so building the containers will work again.
It seemed there were some issues building the cross-platform images. This PR fixes dani-garcia#2501 so building the containers will work again.
This will add a persistent volume check to make sure when running
containers someone is using a volume for persistent storage.
This check can be bypassed if someone configures
I_REALLY_WANT_VOLATILE_STORAGE=true
as an environment variable.This should prevent issues like #2493 .