mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-25 17:25:57 +03:00
[GH-ISSUE #1269] Alpine image doesn't contain sqllite3 command to perform backup #888
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#888
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @80dB on GitHub (Dec 16, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1269
Subject of the issue
It's suggested to run a cron job to backup sqlite3 with the sqlite3 command, however this command isn't installed in the alpine image.
Your environment
Steps to reproduce
Start image and open shell and execute "sqlite3" or "find | grep sql".
Expected behaviour
The sqlite3 command should execute normally.
Actual behaviour
It'll report sqlite3 isn't found.
Work-around
Use the non-alpine image for sqlite3 actions.
@jjlin commented on GitHub (Dec 16, 2020):
Presumably your cron job is running directly on your host system; you should run
sqlite3directly from there as well, installing it if needed,I don't think the
sqlite3package is needed in the Debian-based image, so it should probably be removed.@BlackDex commented on GitHub (Dec 16, 2020):
@jjlin, no, i rather think we need to add it to the alpine image. Or we need to remove the feature from the admin to create a backup. I'm in favor of the first with adding sqlite3 command.
@BlackDex commented on GitHub (Dec 16, 2020):
Though, if creating a cronjob, that job should be on the host though, not within the container.
And it's better to have sqlite3 on the host also to just create a backup via the mapped volume folder.
If you would create a cronjob within the container (which i think isn't possible without installing more software), it will be lost after a new version is being installed.
@jjlin commented on GitHub (Dec 16, 2020):
Ah, I forgot there was a backup function in the admin page. I wonder how many people actually use that, though. Personally, I find it to be of questionable utility, given it doesn't do a complete job (no config, attachments, etc.), and most people would be better off automating it.
@BlackDex commented on GitHub (Dec 18, 2020):
Dockerfiles have been updated to include the libraries.