-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Description
β Have you read and understood the above guidelines?
yes
π What is the name of the script you are using?
vaultwarden.sh
π What was the exact command used to execute the script?
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/vaultwarden.sh)"
βοΈ What settings are you using?
- Default Settings
- Advanced Settings
π₯οΈ Which Linux distribution are you using?
Debian 12
π Provide a clear and concise description of the issue.
If you are using the "update"-command, the script does not check if the installed version is the latest.
Vaultwarden/Webwarden is rebuilt every time without any demand....which logically takes time.
And if the build process is started and you recognize "Oh, it is the same version"...that`s it, you have to wait until it is finished.
In practice and in many cases, an "update"-command results in rebuilding the already installed (latest) version
again and again...until a more current version is available.
Other scripts are checking if the installed version is the latest, so i would mark this as a "Bug".
π Steps to reproduce the issue.
Install Vaultwarden via PVE-Node-Shell:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/vaultwarden.sh)
Run the update command in the LXC and select Vault- or Webwarden to update:
update
β Paste the full error output (if available).
No error output available in this case.
πΌοΈ Additional context (optional).
No response