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 error #166

New Issue
Closed
opened 2026-02-04 16:55:46 +03:00 by OVERLORD · 11 comments
OVERLORD commented 2026-02-04 16:55:46 +03:00
Owner
Copy Link

Originally created by @doozybytes on GitHub (Dec 12, 2024).

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

Linkwarden installation fails with error code.

What settings are you currently utilizing?

  • Default Settings
  • Advanced Settings

Which Linux distribution are you employing?

Debian 12

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

Downloaded async-compression v0.4.18
Downloaded 164 crates (22.6 MB) in 1.75s (largest was openssl-src at 9.9 MB)
\error: failed to compile monolith v2.8.3, intermediate artifacts can be found at /tmp/cargo-install5IttYs

Caused by:
package tokio-util v0.7.13 cannot be built because it requires rustc 1.70 or newer, while the currently active rustc version is 1.63.0
Try re-running cargo install with --locked

[ERROR] in line 41: exit code 0: while executing command $STD cargo install monolith

Please provide detailed steps to reproduce the issue.

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

Originally created by @doozybytes on GitHub (Dec 12, 2024). ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. Linkwarden installation fails with error code. ### What settings are you currently utilizing? - [ ] Default Settings - [X] Advanced Settings ### Which Linux distribution are you employing? Debian 12 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. Downloaded async-compression v0.4.18 Downloaded 164 crates (22.6 MB) in 1.75s (largest was `openssl-src` at 9.9 MB) \error: failed to compile `monolith v2.8.3`, intermediate artifacts can be found at `/tmp/cargo-install5IttYs` Caused by: package `tokio-util v0.7.13` cannot be built because it requires rustc 1.70 or newer, while the currently active rustc version is 1.63.0 Try re-running cargo install with `--locked` [ERROR] in line 41: exit code 0: while executing command $STD cargo install monolith ### Please provide detailed steps to reproduce the issue. Trying to install linkwarden LXC using `bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/linkwarden.sh)"`
OVERLORD added the question label 2026-02-04 16:55:46 +03:00
OVERLORD commented 2026-02-04 16:56:00 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 12, 2024):

Have you installed Monolith?

https://github.com/community-scripts/ProxmoxVE/discussions/305

@MickLesk commented on GitHub (Dec 12, 2024): Have you installed Monolith? https://github.com/community-scripts/ProxmoxVE/discussions/305
OVERLORD commented 2026-02-04 16:56:06 +03:00
Author
Owner
Copy Link

@doozybytes commented on GitHub (Dec 12, 2024):

Have you installed Monolith?

https://github.com/community-scripts/ProxmoxVE/discussions/305

Monolith install is handled by the script.

Failure is actually due to rust version requirement:

package tokio-util v0.7.13 cannot be built because it requires rustc 1.70 or newer, while the currently active rustc version is 1.63.0
@doozybytes commented on GitHub (Dec 12, 2024): > Have you installed Monolith? > > https://github.com/community-scripts/ProxmoxVE/discussions/305 Monolith install is handled by the script. Failure is actually due to rust version requirement: ``` package tokio-util v0.7.13 cannot be built because it requires rustc 1.70 or newer, while the currently active rustc version is 1.63.0 ```
OVERLORD commented 2026-02-04 16:56:13 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 12, 2024):

Okay thats a Clean new Install?

@MickLesk commented on GitHub (Dec 12, 2024): Okay thats a Clean new Install?
OVERLORD commented 2026-02-04 16:56:18 +03:00
Author
Owner
Copy Link

@doozybytes commented on GitHub (Dec 12, 2024):

Okay thats a Clean new Install?

Yes, I just run the script for a new LXC install and get this.

@doozybytes commented on GitHub (Dec 12, 2024): > Okay thats a Clean new Install? Yes, I just run the script for a new LXC install and get this.
OVERLORD commented 2026-02-04 16:56:23 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 13, 2024):

Tested on 2 Devices, Work fine for me:

image

@MickLesk commented on GitHub (Dec 13, 2024): Tested on 2 Devices, Work fine for me: ![image](https://github.com/user-attachments/assets/c4d539c3-dd36-479c-a786-7c1c0d9d9902)
OVERLORD commented 2026-02-04 16:56:29 +03:00
Author
Owner
Copy Link

@doozybytes commented on GitHub (Dec 13, 2024):

Tested on 2 Devices, Work fine for me:

image

Please refer to the issue details, it clearly states Debian

@doozybytes commented on GitHub (Dec 13, 2024): > Tested on 2 Devices, Work fine for me: > > > > ![image](https://github.com/user-attachments/assets/c4d539c3-dd36-479c-a786-7c1c0d9d9902) > > Please refer to the issue details, it clearly states Debian
OVERLORD commented 2026-02-04 16:56:32 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 13, 2024):

image

Its an ubuntu thing. The Default is Debian 12. We could not fix all OS

@MickLesk commented on GitHub (Dec 13, 2024): ![image](https://github.com/user-attachments/assets/a25d683a-4aa1-41f6-8a45-b75e6fa4b301) Its an ubuntu thing. The Default is Debian 12. We could not fix all OS
OVERLORD commented 2026-02-04 16:56:36 +03:00
Author
Owner
Copy Link

@doozybytes commented on GitHub (Dec 13, 2024):

What do you mean? The fail happens with Debian 12....this is an easy dependency fix

@doozybytes commented on GitHub (Dec 13, 2024): What do you mean? The fail happens with Debian 12....this is an easy dependency fix
OVERLORD commented 2026-02-04 16:56:42 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 13, 2024):

Sorry, confused statement, i mean its an debian thing, default is ubuntu for this. Because Debian has another repo and this is older. And Ubuntu runs fine.

@MickLesk commented on GitHub (Dec 13, 2024): Sorry, confused statement, i mean its an debian thing, default is ubuntu for this. Because Debian has another repo and this is older. And Ubuntu runs fine.
OVERLORD commented 2026-02-04 16:56:47 +03:00
Author
Owner
Copy Link

@doozybytes commented on GitHub (Dec 13, 2024):

I understand.

But why not fix the issue if it is known and reported? Why close the ticket and let a known issue be? If other distributions are not supported, clearly indicate it or remove the option.

Leaving this issue persist only creates a worse user experience for anyone not aware where to look for solutions.

@doozybytes commented on GitHub (Dec 13, 2024): I understand. But why not fix the issue if it is known and reported? Why close the ticket and let a known issue be? If other distributions are not supported, clearly indicate it or remove the option. Leaving this issue persist only creates a worse user experience for anyone not aware where to look for solutions.
OVERLORD commented 2026-02-04 16:56:53 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 13, 2024):

Because you accept the guidelines of the Script.
Advanced Settings with another OS are a Breaking Change and we cant fix for every os with every version. Look at the Screenshot of Issue Creating.

Your Script Breaking at this part:

msg_info "Installing Monolith"
$STD cargo install monolith
export PATH=~/.cargo/bin:$PATH
msg_ok "Installed Monolith"

Cargo provides the values matching the OS. If Debian12 provides old or other dependencies, we cannot implement a fix only for this OS

@MickLesk commented on GitHub (Dec 13, 2024): Because you accept the guidelines of the Script. Advanced Settings with another OS are a Breaking Change and we cant fix for every os with every version. Look at the Screenshot of Issue Creating. Your Script Breaking at this part: ```bash msg_info "Installing Monolith" $STD cargo install monolith export PATH=~/.cargo/bin:$PATH msg_ok "Installed Monolith" ``` Cargo provides the values matching the OS. If Debian12 provides old or other dependencies, we cannot implement a fix only for this OS
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 question
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#166
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?