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

Linkwarden Error MSG #583

New Issue
Closed
opened 2025-11-20 04:50:37 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 04:50:37 -05:00
Owner
Copy Link

Originally created by @bignexus on GitHub (Feb 21, 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.

🚀 Creating a Linkwarden LXC using the above default settings

✔️ Using local for Template Storage.
✔️ Using local-lvm for Container Storage.
✔️ Updated LXC Template List
✔️ Downloaded LXC Template
✔️ LXC Container 103 was successfully created.
✔️ Started LXC Container
✔️ Set up Container OS
✔️ Network Connected: 192.168.122.236
✔️ IPv4 Internet Connected
✖️ IPv6 Internet Not Connected
✔️ DNS Resolved github.com to 140.82.121.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
The silent function has suppressed the error, run the script with verbose mode enabled, which will provide more detailed output.

with verbose the follow message:

error: failed to compile monolith v2.8.3, intermediate artifacts can be found at /tmp/cargo-installzCDj5M.
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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Ubuntu 24.10

🔄 Steps to reproduce the issue.

Under Linux Mint with KVM
Im use Proxmox 8.3.1

❌ Paste the full error output (if available).

⠦ Installing Monolith
[ERROR] in line 44: exit code 0: while executing command "$@" > /dev/null 2>&1
The silent function has suppressed the error, run the script with verbose mode enabled, which will provide more detailed output.

with verbose the follwe message:

error: failed to compile monolith v2.8.3, intermediate artifacts can be found at /tmp/cargo-installzCDj5M.
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

🖼️ Additional context (optional).

No response

Originally created by @bignexus on GitHub (Feb 21, 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. 🚀 Creating a Linkwarden LXC using the above default settings ✔️ Using local for Template Storage. ✔️ Using local-lvm for Container Storage. ✔️ Updated LXC Template List ✔️ Downloaded LXC Template ✔️ LXC Container 103 was successfully created. ✔️ Started LXC Container ✔️ Set up Container OS ✔️ Network Connected: 192.168.122.236 ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected ✔️ DNS Resolved github.com to 140.82.121.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 The silent function has suppressed the error, run the script with verbose mode enabled, which will provide more detailed output. with verbose the follow message: error: failed to compile `monolith v2.8.3`, intermediate artifacts can be found at `/tmp/cargo-installzCDj5M`. 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 ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Ubuntu 24.10 ### 🔄 Steps to reproduce the issue. Under Linux Mint with KVM Im use Proxmox 8.3.1 ### ❌ Paste the full error output (if available). ⠦ Installing Monolith [ERROR] in line 44: exit code 0: while executing command "$@" > /dev/null 2>&1 The silent function has suppressed the error, run the script with verbose mode enabled, which will provide more detailed output. with verbose the follwe message: error: failed to compile `monolith v2.8.3`, intermediate artifacts can be found at `/tmp/cargo-installzCDj5M`. 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 ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 04:50:37 -05:00
saavagebueno commented 2025-11-20 04:50:38 -05:00
Author
Owner
Copy Link

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

22.04 only

@MickLesk commented on GitHub (Feb 21, 2025): 22.04 only
saavagebueno commented 2025-11-20 04:50:38 -05:00
Author
Owner
Copy Link

@Staene commented on GitHub (Feb 22, 2025):

I am experiencing the same exact error with an Ubuntu 22.04 LXC.

@Staene commented on GitHub (Feb 22, 2025): I am experiencing the same exact error with an Ubuntu 22.04 LXC.
saavagebueno commented 2025-11-20 04:50:38 -05:00
Author
Owner
Copy Link

@MaouSenkrad commented on GitHub (Feb 23, 2025):

I wasn't able to install with default settings, same error as others.
I changed to Ubuntu 24.10 and it installed without error, but after some use it seems to have performance issues and crashes (which I expect, if unsupported).

@MaouSenkrad commented on GitHub (Feb 23, 2025): I wasn't able to install with default settings, same error as others. I changed to Ubuntu 24.10 and it installed without error, but after some use it seems to have performance issues and crashes (which I expect, if unsupported).
saavagebueno commented 2025-11-20 04:50:38 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 3, 2025):

done

@MickLesk commented on GitHub (Mar 3, 2025): done
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 bug
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#583
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?