[GH-ISSUE #6314] Prebuild-Archive possible? Excessive RAM requirements for Vaultwarden builds (>= 7GB during install/update) #11211

New Issue

GiteaMirror · 2026-04-20T14:45:38-05:00

GiteaMirror commented

2026-04-20 14:45:38 -05:00

Originally created by @MickLesk on GitHub (Sep 23, 2025).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6314

Prerequisites

I have searched the existing Closed AND Open Issues AND Discussions
I have searched and read the documentation

Vaultwarden Support String

https://github.com/community-scripts/ProxmoxVE/discussions/7485#discussioncomment-14477661

The installation/update script for Vaultwarden is one of the most used in our collection, with over 12,500 tracked installations in the last 5 months.

The main pain point:

During installation or update, the script builds Vaultwarden from source.
This build step requires at least 7 GB of RAM (cargo build --release).
After the build, Vaultwarden runs perfectly fine with ~400–500 MB RAM in production.

This creates a real problem for many home lab users who run on older hardware (e.g. DELL/Lenovo desktops with only 8 GB total system RAM). For them, updates regularly fail unless they manually increase RAM to 7 GB just for the build.

Why this matters

Vaultwarden is extremely popular in the homelab community.
The update/install process should be reliable and usable even on lower-RAM systems.
Alpine/Docker variants show that prebuilt binaries or lighter builds are possible:
- Debian 13 native: build requires 7 GB RAM, runtime ~400 MB
- Alpine native: runtime ~15 MB RAM, no build required
- Docker Alpine: runtime ~65 MB RAM

Request

Would it be possible to:

Provide prebuilt release binaries (Debian/Ubuntu compatible), or
Adjust the build/update process in a way that avoids these extreme memory requirements?

This would massively improve usability for the majority of homelab setups.

Vaultwarden Build Version

latest

Deployment method

Build from source

Custom deployment method

Relevant script section

msg_info "Building Vaultwarden ${VAULT} (Patience)"
$STD git clone https://github.com/dani-garcia/vaultwarden
cd vaultwarden
$STD cargo build --features "sqlite,mysql,postgresql" --release
msg_ok "Built Vaultwarden ${VAULT}"

Reverse Proxy

nvm

Host/Server Operating System

Linux

Operating System Version

Debian 12 / 13

Clients

Web Vault, CLI

Client Version

latest

Steps To Reproduce

Deploy our Script on Proxmox Host:
https://community-scripts.github.io/ProxmoxVE/scripts?id=vaultwarden

=> or do an manual build with rust git clone and cargo

Expected Result

Prebuild or other Solution to reduce the RAM

Actual Result

RAM explode during Install / Update

Logs

Screenshots or Videos

No response

Additional Context

No response

Originally created by @MickLesk on GitHub (Sep 23, 2025). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6314 ### Prerequisites - [x] I have searched the existing **Closed _AND_ Open** [Issues](https://github.com/dani-garcia/vaultwarden/issues?q=is%3Aissue%20) **_AND_** [Discussions](https://github.com/dani-garcia/vaultwarden/discussions?discussions_q=) - [x] I have searched and read the [documentation](https://github.com/dani-garcia/vaultwarden/wiki/) ### Vaultwarden Support String https://github.com/community-scripts/ProxmoxVE/discussions/7485#discussioncomment-14477661 The installation/update script for **Vaultwarden** is one of the most used in our collection, with over **12,500 tracked installations in the last 5 months**. The main pain point: - During **installation or update**, the script builds Vaultwarden from source. - This build step requires at least **7 GB of RAM** (`cargo build --release`). - After the build, Vaultwarden runs perfectly fine with ~**400–500 MB RAM** in production. This creates a real problem for many home lab users who run on older hardware (e.g. DELL/Lenovo desktops with only 8 GB total system RAM). For them, updates regularly fail unless they manually increase RAM to 7 GB just for the build. ## Why this matters - Vaultwarden is extremely popular in the homelab community. - The update/install process should be reliable and usable even on lower-RAM systems. - Alpine/Docker variants show that **prebuilt binaries** or lighter builds are possible: - Debian 13 native: build requires 7 GB RAM, runtime ~400 MB - Alpine native: runtime ~15 MB RAM, no build required - Docker Alpine: runtime ~65 MB RAM ## Request Would it be possible to: - Provide **prebuilt release binaries** (Debian/Ubuntu compatible), or - Adjust the build/update process in a way that avoids these extreme memory requirements? This would massively improve usability for the majority of homelab setups. ### Vaultwarden Build Version latest ### Deployment method Build from source ### Custom deployment method ## Relevant script section ```bash msg_info "Building Vaultwarden ${VAULT} (Patience)" $STD git clone https://github.com/dani-garcia/vaultwarden cd vaultwarden $STD cargo build --features "sqlite,mysql,postgresql" --release msg_ok "Built Vaultwarden ${VAULT}" ``` ### Reverse Proxy nvm ### Host/Server Operating System Linux ### Operating System Version Debian 12 / 13 ### Clients Web Vault, CLI ### Client Version latest ### Steps To Reproduce Deploy our Script on Proxmox Host: https://community-scripts.github.io/ProxmoxVE/scripts?id=vaultwarden => or do an manual build with rust git clone and cargo ### Expected Result - Prebuild or other Solution to reduce the RAM ### Actual Result - RAM explode during Install / Update ### Logs ```text ``` ### Screenshots or Videos _No response_ ### Additional Context _No response_

GiteaMirror added the bug label 2026-04-20 14:45:38 -05:00

GiteaMirror closed this issue

2026-04-20 14:45:38 -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#11211