[PR #4845] Include sqlite3 binaries in Docker images #2722

New Issue

OVERLORD · 2025-10-09T18:10:21+03:00

OVERLORD commented

2025-10-09 18:10:21 +03:00

Original Pull Request: https://github.com/dani-garcia/vaultwarden/pull/4845

State: closed
Merged: No

I understand that the runtime docker images are trimmed down for size. Regardless, I think that it makes sense to have the sqlite3 binaries as part of the images because it makes backups way easier without having to resort to other images/containers or having sqlite installed on the docker host.

A cron-driven backup on the Docker host would then just be similar to the following cronjob (assuming a running container named vaultwarden)

0 0 * * * root /usr/bin/docker exec vaultwarden sqlite3 /data/db.sqlite3 "VACUUM INTO '/backup/db-$(date '+%Y%m%d-%H%M').sqlite3'"

If size of the images is more important, I understand, please decline the PR.

**Original Pull Request:** https://github.com/dani-garcia/vaultwarden/pull/4845 **State:** closed **Merged:** No --- I understand that the runtime docker images are trimmed down for size. Regardless, I think that it makes sense to have the sqlite3 binaries as part of the images because it makes backups way easier without having to resort to other images/containers or having sqlite installed on the docker host. A cron-driven backup on the Docker host would then just be similar to the following cronjob (assuming a running container named `vaultwarden`) ``` 0 0 * * * root /usr/bin/docker exec vaultwarden sqlite3 /data/db.sqlite3 "VACUUM INTO '/backup/db-$(date '+%Y%m%d-%H%M').sqlite3'" ``` If size of the images is more important, I understand, please decline the PR.

OVERLORD added the pull-request label 2025-10-09 18:10:21 +03:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#2722