starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Linkwarden installation (Advanced Settings) failed on Monolith #340

New Issue
Closed
opened 2026-02-04 18:04:15 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-04 18:04:15 +03:00
Owner
Copy Link

Originally created by @LucasJanin on GitHub (Jan 15, 2025).

✅ Have you read and understood the above guidelines?

Yes

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

Linkwarden

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

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/linkwarden.sh)"

📝 Provide a clear and concise description of the issue.

Failed installation during Installing Monolith with Advanced Settings

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Choose Distribution: Debian
Choose version: 12 Bookworm
Choose Type: 1 Unprivileged
Disable IPv6: Yes
Enable Root SSH Access: Yes
SSH key: xxxxxx
Enable Verbose Mode: No

❌ Paste the full error output (if available).

🧩 Using Advanced Settings on node nab5
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Unprivileged
🔐 Root Password: ********
🆔 Container ID: 108
🏠 Hostname: linkwarden
💾 Disk Size: 12 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 2048 MiB
🌉 Bridge: vmbr0
📡 IP Address: dhcp
🌐 Gateway IP Address: Default
📡 APT-Cacher IP Address: 192.168.1.232 (try without, same result)
🚫 Disable IPv6: yes
⚙️ Interface MTU Size: Default
🔍 DNS Search Domain: Host
📡 DNS Server IP Address: Host
🏷️ Vlan: Default
📡 Tags: community-script;bookmark
🔑 Root SSH Access: yes
Warning: No SSH key provided.
🔍 Verbose Mode: no
🚀 Creating a Linkwarden LXC using the above advanced settings
✔️ Using local for Template Storage.
✔️ Using local-lvm for Container Storage.
✔️ Updated LXC Template List
✔️ LXC Container 108 was successfully created.
✔️ Started LXC Container
✔️ Set up Container OS
✔️ Network Connected: 192.168.1.194
✔️ IPv4 Internet Connected
✖️ IPv6 Internet Not Connected
✔️ DNS Resolved github.com to 140.82.112.4
✔️ Updated Container OS
✔️ Installed Dependencies
✔️ Set up Node.js Repository
✔️ Installed Node.js/Yarn
⠴ Installing Monolith
[ERROR] in line 44: exit code 0: while executing command "$@" > /dev/null 2>&1

🖼️ Additional context (optional).

The default setting is working fine

Originally created by @LucasJanin on GitHub (Jan 15, 2025). ### ✅ Have you read and understood the above guidelines? Yes ### 📜 What is the name of the script you are using? Linkwarden ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/linkwarden.sh)" ### 📝 Provide a clear and concise description of the issue. Failed installation during Installing Monolith with Advanced Settings ### ⚙️ What settings are you using? - [ ] Default Settings - [X] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Choose Distribution: Debian Choose version: 12 Bookworm Choose Type: 1 Unprivileged Disable IPv6: Yes Enable Root SSH Access: Yes SSH key: xxxxxx Enable Verbose Mode: No ### ❌ Paste the full error output (if available). 🧩 Using Advanced Settings on node nab5 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 🔐 Root Password: ******** 🆔 Container ID: 108 🏠 Hostname: linkwarden 💾 Disk Size: 12 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🌉 Bridge: vmbr0 📡 IP Address: dhcp 🌐 Gateway IP Address: Default 📡 APT-Cacher IP Address: 192.168.1.232 (try without, same result) 🚫 Disable IPv6: yes ⚙️ Interface MTU Size: Default 🔍 DNS Search Domain: Host 📡 DNS Server IP Address: Host 🏷️ Vlan: Default 📡 Tags: community-script;bookmark 🔑 Root SSH Access: yes Warning: No SSH key provided. 🔍 Verbose Mode: no 🚀 Creating a Linkwarden LXC using the above advanced settings ✔️ Using local for Template Storage. ✔️ Using local-lvm for Container Storage. ✔️ Updated LXC Template List ✔️ LXC Container 108 was successfully created. ✔️ Started LXC Container ✔️ Set up Container OS ✔️ Network Connected: 192.168.1.194 ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected ✔️ DNS Resolved github.com to 140.82.112.4 ✔️ Updated Container OS ✔️ Installed Dependencies ✔️ Set up Node.js Repository ✔️ Installed Node.js/Yarn ⠴ Installing Monolith [ERROR] in line 44: exit code 0: while executing command "$@" > /dev/null 2>&1 ### 🖼️ Additional context (optional). The default setting is working fine
OVERLORD added the not a script issue🛑 Failure to comply with the guidelines labels 2026-02-04 18:04:15 +03:00
OVERLORD commented 2026-02-04 18:04:28 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 15, 2025):

We only support custom os on issues.

"🛠️ Supported environments only: Ensure you are using a default Linux distribution. Custom setups may not be supported."

@MickLesk commented on GitHub (Jan 15, 2025): We only support custom os on issues. "🛠️ Supported environments only: Ensure you are using a default Linux distribution. Custom setups may not be supported."
OVERLORD commented 2026-02-04 18:04:31 +03:00
Author
Owner
Copy Link

@jonasduever commented on GitHub (Jan 15, 2025):

@LucasJanin Just FYI, since I had the same issue: The reason seems to be that Debian 12 stable only includes rustc 1.63.0, which is too old for the monolith dependency.

root@linkwarden:~# cargo install monolith
    Updating crates.io index
  Installing monolith v2.8.3
error: failed to compile `monolith v2.8.3`, intermediate artifacts can be found at `/tmp/cargo-installHYrYc3`

Caused by:
  package `tower v0.5.2` cannot be built because it requires rustc 1.64.0 or newer, while the currently active rustc version is 1.63.0
  Try re-running cargo install with `--locked`

Using the default OS (Ubuntu 22.04) works fine.

@jonasduever commented on GitHub (Jan 15, 2025): @LucasJanin Just FYI, since I had the same issue: The reason seems to be that Debian 12 stable only includes `rustc` 1.63.0, which is too old for the `monolith` dependency. ``` root@linkwarden:~# cargo install monolith Updating crates.io index Installing monolith v2.8.3 error: failed to compile `monolith v2.8.3`, intermediate artifacts can be found at `/tmp/cargo-installHYrYc3` Caused by: package `tower v0.5.2` cannot be built because it requires rustc 1.64.0 or newer, while the currently active rustc version is 1.63.0 Try re-running cargo install with `--locked` ``` Using the default OS (Ubuntu 22.04) works fine.
OVERLORD commented 2026-02-04 18:04:47 +03:00
Author
Owner
Copy Link

@elronat commented on GitHub (Feb 20, 2025):

I have just tried to use the script and unfortunately failed with exactly the same error. I have also tried the other options and get the same errors.

⠸ Downloaded 158 crates (22.6 MB) in 1.17s (largest was openssl-srcat 10.0 MB) error: failed to compilemonolith v2.8.3, intermediate artifacts can be found at /tmp/cargo-install2mT36P. To reuse those artifacts with a future compilation, set the environment variable CARGO_TARGET_DIR` to that path.

Caused by:
package native-tls v0.2.14 cannot be built because it requires rustc 1.80.0 or newer, while the currently active rustc version is 1.75.0
Try re-running cargo install with --locked
⠼
[ERROR] in line 41: exit code 0: while executing command $STD cargo install monolith

@elronat commented on GitHub (Feb 20, 2025): I have just tried to use the script and unfortunately failed with exactly the same error. I have also tried the other options and get the same errors. > `⠸ Downloaded 158 crates (22.6 MB) in 1.17s (largest was `openssl-src` at 10.0 MB) > error: failed to compile `monolith v2.8.3`, intermediate artifacts can be found at `/tmp/cargo-install2mT36P`. > To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path. > > Caused by: > package `native-tls v0.2.14` cannot be built because it requires rustc 1.80.0 or newer, while the currently active rustc version is 1.75.0 > Try re-running cargo install with `--locked` > ⠼ > [ERROR] in line 41: exit code 0: while executing command $STD cargo install monolith
OVERLORD commented 2026-02-04 18:05:04 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 20, 2025):

have you followed the guide?

@MickLesk commented on GitHub (Feb 20, 2025): have you followed the guide?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
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
🛑 Failure to comply with the guidelines
No Label not a script issue 🛑 Failure to comply with the guidelines
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#340
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?