SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Vaultwarden update #70

New Issue
Closed
opened 2025-11-20 04:43:18 -05:00 by saavagebueno · 9 comments
saavagebueno commented 2025-11-20 04:43:18 -05:00
Owner
Copy Link

Originally created by @vdias on GitHub (Nov 18, 2024).

Originally assigned to: @havardthom on GitHub.

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

| Updating VaultWarden to 1.32.5 (Patience)
[ERROR] in line 87: exit code 0: while executing command cargo build --features "sqlite,mysql,postgresql" --release &> /dev/null

What settings are you currently utilizing?

Default Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

No response

Please provide detailed steps to reproduce the issue.

Launch .sh script to update version.
bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/vaultwarden.sh)"

Originally created by @vdias on GitHub (Nov 18, 2024). Originally assigned to: @havardthom on GitHub. ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. | Updating VaultWarden to 1.32.5 (Patience) [ERROR] in line 87: exit code 0: while executing command cargo build --features "sqlite,mysql,postgresql" --release &> /dev/null ### What settings are you currently utilizing? Default Settings ### Which Linux distribution are you employing? Debian 12 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. _No response_ ### Please provide detailed steps to reproduce the issue. Launch .sh script to update version. bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/vaultwarden.sh)"
saavagebueno added the not a script issue label 2025-11-20 04:43:18 -05:00
saavagebueno commented 2025-11-20 04:43:19 -05:00
Author
Owner
Copy Link

@vdias commented on GitHub (Nov 20, 2024):

Any update on this one?

@vdias commented on GitHub (Nov 20, 2024): Any update on this one?
saavagebueno commented 2025-11-20 04:43:19 -05:00
Author
Owner
Copy Link

@havardthom commented on GitHub (Nov 20, 2024):

I am not able to recreate this issue, update worked fine here. Could this be related to https://github.com/community-scripts/ProxmoxVE/issues/236 ? Do you have enough resources allocated to the LXC? 4 CPU cores and 6GB RAM minimum. Do you have enough storage?

@havardthom commented on GitHub (Nov 20, 2024): I am not able to recreate this issue, update worked fine here. Could this be related to https://github.com/community-scripts/ProxmoxVE/issues/236 ? Do you have enough resources allocated to the LXC? 4 CPU cores and 6GB RAM minimum. Do you have enough storage?
saavagebueno commented 2025-11-20 04:43:19 -05:00
Author
Owner
Copy Link

@vdias commented on GitHub (Nov 20, 2024):

6 vCPU
7GB RAM
11.06 GiB used of 11.71 GiB

Disk could be the problem... but cannot understand how can vaultwarden use 11GiB...

@vdias commented on GitHub (Nov 20, 2024): 6 vCPU 7GB RAM 11.06 GiB used of 11.71 GiB Disk could be the problem... but cannot understand how can vaultwarden use 11GiB...
saavagebueno commented 2025-11-20 04:43:19 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 20, 2024):

6 vCPU
7GB RAM
11.06 GiB used of 11.71 GiB

Disk could be the problem... but cannot understand how can vaultwarden use 11GiB...

Thats an Problem.
Vaultwarden on GNU Systems use many storage, the most of this are from the Cargo Builds.

@MickLesk commented on GitHub (Nov 20, 2024): > 6 vCPU > 7GB RAM > 11.06 GiB used of 11.71 GiB > > Disk could be the problem... but cannot understand how can vaultwarden use 11GiB... > Thats an Problem. Vaultwarden on GNU Systems use many storage, the most of this are from the Cargo Builds.
saavagebueno commented 2025-11-20 04:43:19 -05:00
Author
Owner
Copy Link

@havardthom commented on GitHub (Nov 20, 2024):

Feel free to investigate the disk usage and report back if something is wrong

@havardthom commented on GitHub (Nov 20, 2024): Feel free to investigate the disk usage and report back if something is wrong
saavagebueno commented 2025-11-20 04:43:20 -05:00
Author
Owner
Copy Link

@vdias commented on GitHub (Nov 20, 2024):

root@vaultwarden:~# du -h | sort -hr | head -n 30
7.7G .
4.9G ./.rustup/toolchains
4.9G ./.rustup
1.9G ./.cargo/registry
1.9G ./.cargo
1.1G ./.cargo/registry/src
936M ./vaultwarden
922M ./vaultwarden/target/release
922M ./vaultwarden/target
854M ./vaultwarden/target/release/deps
759M ./.cargo/registry/src/index.crates.io-6f17d22bba15001f
617M ./.cargo/registry/index
594M ./.cargo/registry/index/github.com-1ecc6299db9ec823
576M ./.cargo/registry/index/github.com-1ecc6299db9ec823/.git/objects/pack
576M ./.cargo/registry/index/github.com-1ecc6299db9ec823/.git/objects
576M ./.cargo/registry/index/github.com-1ecc6299db9ec823/.git
570M ./.rustup/toolchains/1.72.0-x86_64-unknown-linux-gnu
525M ./.rustup/toolchains/1.82.0-x86_64-unknown-linux-gnu
512M ./.rustup/toolchains/1.67.0-x86_64-unknown-linux-gnu
506M ./.rustup/toolchains/1.69.0-x86_64-unknown-linux-gnu
505M ./.rustup/toolchains/1.75.0-x86_64-unknown-linux-gnu
487M ./.rustup/toolchains/1.80.1-x86_64-unknown-linux-gnu
480M ./.rustup/toolchains/1.79.0-x86_64-unknown-linux-gnu
479M ./.rustup/toolchains/1.72.0-x86_64-unknown-linux-gnu/lib
471M ./.rustup/toolchains/stable-x86_64-unknown-linux-gnu
471M ./.rustup/toolchains/1.65.0-x86_64-unknown-linux-gnu
470M ./.rustup/toolchains/1.77.0-x86_64-unknown-linux-gnu
458M ./.rustup/toolchains/1.67.0-x86_64-unknown-linux-gnu/lib
452M ./.rustup/toolchains/1.69.0-x86_64-unknown-linux-gnu/lib
449M ./.rustup/toolchains/1.82.0-x86_64-unknown-linux-gnu/lib

@vdias commented on GitHub (Nov 20, 2024): root@vaultwarden:~# du -h | sort -hr | head -n 30 7.7G . 4.9G ./.rustup/toolchains 4.9G ./.rustup 1.9G ./.cargo/registry 1.9G ./.cargo 1.1G ./.cargo/registry/src 936M ./vaultwarden 922M ./vaultwarden/target/release 922M ./vaultwarden/target 854M ./vaultwarden/target/release/deps 759M ./.cargo/registry/src/index.crates.io-6f17d22bba15001f 617M ./.cargo/registry/index 594M ./.cargo/registry/index/github.com-1ecc6299db9ec823 576M ./.cargo/registry/index/github.com-1ecc6299db9ec823/.git/objects/pack 576M ./.cargo/registry/index/github.com-1ecc6299db9ec823/.git/objects 576M ./.cargo/registry/index/github.com-1ecc6299db9ec823/.git 570M ./.rustup/toolchains/1.72.0-x86_64-unknown-linux-gnu 525M ./.rustup/toolchains/1.82.0-x86_64-unknown-linux-gnu 512M ./.rustup/toolchains/1.67.0-x86_64-unknown-linux-gnu 506M ./.rustup/toolchains/1.69.0-x86_64-unknown-linux-gnu 505M ./.rustup/toolchains/1.75.0-x86_64-unknown-linux-gnu 487M ./.rustup/toolchains/1.80.1-x86_64-unknown-linux-gnu 480M ./.rustup/toolchains/1.79.0-x86_64-unknown-linux-gnu 479M ./.rustup/toolchains/1.72.0-x86_64-unknown-linux-gnu/lib 471M ./.rustup/toolchains/stable-x86_64-unknown-linux-gnu 471M ./.rustup/toolchains/1.65.0-x86_64-unknown-linux-gnu 470M ./.rustup/toolchains/1.77.0-x86_64-unknown-linux-gnu 458M ./.rustup/toolchains/1.67.0-x86_64-unknown-linux-gnu/lib 452M ./.rustup/toolchains/1.69.0-x86_64-unknown-linux-gnu/lib 449M ./.rustup/toolchains/1.82.0-x86_64-unknown-linux-gnu/lib
saavagebueno commented 2025-11-20 04:43:20 -05:00
Author
Owner
Copy Link

@vdias commented on GitHub (Nov 20, 2024):

root@vaultwarden:~# rustup show
Default host: x86_64-unknown-linux-gnu
rustup home: /root/.rustup

installed toolchains

stable-x86_64-unknown-linux-gnu (default)
1.65.0-x86_64-unknown-linux-gnu
1.67.0-x86_64-unknown-linux-gnu
1.69.0-x86_64-unknown-linux-gnu
1.72.0-x86_64-unknown-linux-gnu
1.75.0-x86_64-unknown-linux-gnu
1.77.0-x86_64-unknown-linux-gnu
1.79.0-x86_64-unknown-linux-gnu
1.80.1-x86_64-unknown-linux-gnu
1.82.0-x86_64-unknown-linux-gnu

active toolchain

stable-x86_64-unknown-linux-gnu (default)
rustc 1.65.0 (897e37553 2022-11-02)

Could be a good idea to add a rust cleanup task...

@vdias commented on GitHub (Nov 20, 2024): root@vaultwarden:~# rustup show Default host: x86_64-unknown-linux-gnu rustup home: /root/.rustup installed toolchains -------------------- stable-x86_64-unknown-linux-gnu (default) 1.65.0-x86_64-unknown-linux-gnu 1.67.0-x86_64-unknown-linux-gnu 1.69.0-x86_64-unknown-linux-gnu 1.72.0-x86_64-unknown-linux-gnu 1.75.0-x86_64-unknown-linux-gnu 1.77.0-x86_64-unknown-linux-gnu 1.79.0-x86_64-unknown-linux-gnu 1.80.1-x86_64-unknown-linux-gnu 1.82.0-x86_64-unknown-linux-gnu active toolchain ---------------- stable-x86_64-unknown-linux-gnu (default) rustc 1.65.0 (897e37553 2022-11-02) Could be a good idea to add a rust cleanup task...
saavagebueno commented 2025-11-20 04:43:20 -05:00
Author
Owner
Copy Link

@vdias commented on GitHub (Nov 20, 2024):

Really prefer the LXC concept... but this problems do not affect docker...

@vdias commented on GitHub (Nov 20, 2024): Really prefer the LXC concept... but this problems do not affect docker...
saavagebueno commented 2025-11-20 04:43:20 -05:00
Author
Owner
Copy Link

@vdias commented on GitHub (Nov 20, 2024):

Fixed, cleaning up rust toolchains.
rustup toolchain uninstall XXXXXXXXXXXXXXXXXXXXX

root@vaultwarden:/# rustup show
Default host: x86_64-unknown-linux-gnu
rustup home:  /root/.rustup

installed toolchains
--------------------

stable-x86_64-unknown-linux-gnu (default)
1.82.0-x86_64-unknown-linux-gnu

active toolchain
----------------

stable-x86_64-unknown-linux-gnu (default)
rustc 1.82.0 (f6e511eec 2024-10-15)
@vdias commented on GitHub (Nov 20, 2024): Fixed, cleaning up rust toolchains. `rustup toolchain uninstall XXXXXXXXXXXXXXXXXXXXX` ``` root@vaultwarden:/# rustup show Default host: x86_64-unknown-linux-gnu rustup home: /root/.rustup installed toolchains -------------------- stable-x86_64-unknown-linux-gnu (default) 1.82.0-x86_64-unknown-linux-gnu active toolchain ---------------- stable-x86_64-unknown-linux-gnu (default) rustc 1.82.0 (f6e511eec 2024-10-15) ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label not a script issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#70
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?