starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-26 09:46:06 +03:00

[GH-ISSUE #11919] Vaultwarden update "Alpine" #2504

New issue

Closed

opened 2026-02-26 12:52:40 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 12:52:40 +03:00

Owner

Originally created by @Blastmun on GitHub (Feb 14, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11919

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 What is the name of the script you are using?

Vaultwarden

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/alpine-vaultwarden.sh)"

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Alpine

📈 Which Proxmox version are you on?

8.4.16

📝 Provide a clear and concise description of the issue.

Hello, I'm not sure if the error is on my side, but I can't update my Vaultwarden to version 1.35.3. When I run the command in the LXC, it returns "✔️ Updated successfully!".

Alpine-Vaultwarden LXC Container
    🌐   Provided by: community-scripts ORG | GitHub: https://github.com/community-scripts/ProxmoxVE

    🖥️   OS: Alpine Linux - Version: 3.23.3
    🏠   Hostname: alpine-vaultwarden
    💡   IP Address: 192.168.1.76

 📋 Vaultwarden Update Options

      * 1) Update Vaultwarden
        2) Reset ADMIN_TOKEN

      Select [default=1, timeout 10s]: 1
OK: 163.0 MiB in 115 packages
  ✔️   Updated successfully!

However, on the web side, it still shows 1.35.2. After restarting, the issue persists. I even did a fresh installation to see the result, and it still shows version 1.35.2.

🔄 Steps to reproduce the issue.

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/alpine-vaultwarden.sh)"

❌ Paste the full error output (if available).

Alpine-Vaultwarden LXC Container
🌐 Provided by: community-scripts ORG | GitHub: https://github.com/community-scripts/ProxmoxVE

🖥️   OS: Alpine Linux - Version: 3.23.3
🏠   Hostname: alpine-vaultwarden
💡   IP Address: 192.168.1.76

📋 Vaultwarden Update Options

  * 1) Update Vaultwarden
    2) Reset ADMIN_TOKEN

  Select [default=1, timeout 10s]: 1

OK: 163.0 MiB in 115 packages
✔️ Updated successfully!

🖼️ Additional context (optional).

No response

Originally created by @Blastmun on GitHub (Feb 14, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11919 ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? Vaultwarden ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/alpine-vaultwarden.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Alpine ### 📈 Which Proxmox version are you on? 8.4.16 ### 📝 Provide a clear and concise description of the issue. Hello, I'm not sure if the error is on my side, but I can't update my Vaultwarden to version 1.35.3. When I run the command in the LXC, it returns "✔️ Updated successfully!". ``` Alpine-Vaultwarden LXC Container 🌐 Provided by: community-scripts ORG | GitHub: https://github.com/community-scripts/ProxmoxVE 🖥️ OS: Alpine Linux - Version: 3.23.3 🏠 Hostname: alpine-vaultwarden 💡 IP Address: 192.168.1.76 📋 Vaultwarden Update Options * 1) Update Vaultwarden 2) Reset ADMIN_TOKEN Select [default=1, timeout 10s]: 1 OK: 163.0 MiB in 115 packages ✔️ Updated successfully! ``` However, on the web side, it still shows 1.35.2. After restarting, the issue persists. I even did a fresh installation to see the result, and it still shows version 1.35.2. <img width="848" height="615" alt="Image" src="https://github.com/user-attachments/assets/bae2248e-604e-4ed6-89e0-781a7663e2d6" /> ### 🔄 Steps to reproduce the issue. bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/alpine-vaultwarden.sh)" ### ❌ Paste the full error output (if available). Alpine-Vaultwarden LXC Container 🌐 Provided by: community-scripts ORG | GitHub: https://github.com/community-scripts/ProxmoxVE 🖥️ OS: Alpine Linux - Version: 3.23.3 🏠 Hostname: alpine-vaultwarden 💡 IP Address: 192.168.1.76 📋 Vaultwarden Update Options * 1) Update Vaultwarden 2) Reset ADMIN_TOKEN Select [default=1, timeout 10s]: 1 OK: 163.0 MiB in 115 packages ✔️ Updated successfully! ### 🖼️ Additional context (optional). _No response_

kerem

2026-02-26 12:52:40 +03:00

closed this issue
added the
not a script issue
label

kerem commented

2026-02-26 12:52:40 +03:00

Author

Owner

@MickLesk commented on GitHub (Feb 14, 2026):

Alpine packages are Not maintained by their Developer. This Versions are never directly updated

https://pkgs.alpinelinux.org/package/v3.23/community/x86_64/vaultwarden

@MickLesk commented on GitHub (Feb 14, 2026): Alpine packages are Not maintained by their Developer. This Versions are never directly updated https://pkgs.alpinelinux.org/package/v3.23/community/x86_64/vaultwarden

kerem commented

2026-02-26 12:52:40 +03:00

Author

Owner

@Blastmun commented on GitHub (Feb 15, 2026):

thank you for the answer, I will think about switching to classic Debian, however it seems enormous to me the difference in resources between the two installations

@Blastmun commented on GitHub (Feb 15, 2026): thank you for the answer, I will think about switching to classic Debian, however it seems enormous to me the difference in resources between the two installations

kerem referenced this issue

2026-02-26 13:34:41 +03:00

[PR #2504] [CLOSED] Add ZFS to Podman. Now it works on ZFS! #3798

kerem referenced this issue

2026-02-26 13:34:44 +03:00

[PR #2526] [MERGED] Add ZFS to Podman. Now it works on ZFS! #3811

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#2504

No description provided.

Rows
Columns