[PR #4845] [CLOSED] Include sqlite3 binaries in Docker images #27073

New Issue

GiteaMirror · 2026-06-15T14:25:09-05:00

GiteaMirror commented

2026-06-15 14:25:09 -05:00

📋 Pull Request Information

Original PR: https://github.com/dani-garcia/vaultwarden/pull/4845
Author: @capi
Created: 8/12/2024
Status: ❌ Closed

Base: main ← Head: add-sqlite3-to-docker-images

📝 Commits (1)

ba7659c Include sqlite3 binaries in Docker images

📊 Changes

3 files changed (+8 additions, -4 deletions)

View changed files

📝 docker/Dockerfile.alpine (+2 -1)
📝 docker/Dockerfile.debian (+2 -1)
📝 docker/Dockerfile.j2 (+4 -2)

📄 Description

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.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/dani-garcia/vaultwarden/pull/4845 **Author:** [@capi](https://github.com/capi) **Created:** 8/12/2024 **Status:** ❌ Closed **Base:** `main` ← **Head:** `add-sqlite3-to-docker-images` --- ### 📝 Commits (1) - [`ba7659c`](https://github.com/dani-garcia/vaultwarden/commit/ba7659c3c6956558c4f33a25b8f9a83fd0362b11) Include sqlite3 binaries in Docker images ### 📊 Changes **3 files changed** (+8 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `docker/Dockerfile.alpine` (+2 -1) 📝 `docker/Dockerfile.debian` (+2 -1) 📝 `docker/Dockerfile.j2` (+4 -2) </details> ### 📄 Description 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-06-15 14:25:09 -05:00

GiteaMirror closed this issue

2026-06-15 14:25:10 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#27073