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

Karakeep - install error #987

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

Originally created by @JohnyBeGood on GitHub (May 20, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Karakeep

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📝 Provide a clear and concise description of the issue.

Unable to install inside the Proxmox.

🔄 Steps to reproduce the issue.

Start either standard or advanced install. It will show an error at the end (/dev/fd/63: line 73: SPINNER_PID: unbound variable) and complain there is no network. Even though the error is shown, it creates the container.
At one point I had few of them running.
Updated Proxmox and rebooted, made sure there was a network connection. It does not make any difference.

❌ Paste the full error output (if available).

/ /______ __________ / /____ ___ ____
/ /// __ / ___/ __ / /// _ / _ / __
/ ,< / // / / / // / ,< / / / // /
//||_,// _,//||_/_/ .__/
//
🧩 Using Advanced Settings on node pve-main
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Unprivileged
🔐 Root Password: ********
🆔 Container ID: 128
🏠 Hostname: karakeep
💾 Disk Size: 20 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 4096 MiB
🌉 Bridge: vmbr0
📡 IP Address: dhcp
🌐 Gateway IP Address: Default
📡 APT-Cacher IP Address: Default
🚫 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
🔍 Verbose Mode: yes
🚀 Creating a karakeep LXC using the above advanced settings
✔️ Using local for Template Storage.
✔️ Using local-zfs for Container Storage.
✔️ Updated LXC Template List
✔️ LXC Template is ready to use.
✔️ LXC Container 128 was successfully created.
✔️ Started LXC Container
net.ipv6.conf.all.disable_ipv6 = 1
⠹ ✖️ No Network! ner OS
✖️ No Network After 10 Tries
📡 Check Network Settings
/dev/fd/63: line 73: SPINNER_PID: unbound variable
root@pve-main:~#

🖼️ Additional context (optional).

Did another advanced install with verbose:

__                    __

/ /______ __________ / /____ ___ ____
/ /// __ / ___/ __ / /// _ / _ / __
/ ,< / // / / / // / ,< / / / // /
//||_,// _,//||_/_/ .__/
//
🧩 Using Advanced Settings on node pve-main
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Unprivileged
🔐 Root Password: ********
🆔 Container ID: 125
🏠 Hostname: karakeep
💾 Disk Size: 20 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 4096 MiB
🌉 Bridge: vmbr0
📡 IP Address: dhcp
🌐 Gateway IP Address: Default
📡 APT-Cacher IP Address: Default
🚫 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
🔍 Verbose Mode: yes
🚀 Creating a karakeep LXC using the above advanced settings
✔️ Using local for Template Storage.
✔️ Using local-zfs for Container Storage.
✔️ Updated LXC Template List
✔️ LXC Template is ready to use.
✔️ LXC Container 125 was successfully created.
✔️ Started LXC Container
net.ipv6.conf.all.disable_ipv6 = 1
⠹ ✖️ No Network! ner OS
✖️ No Network After 10 Tries
📡 Check Network Settings
/dev/fd/63: line 73: SPINNER_PID: unbound variable
root@pve-main:~#

No response

Originally created by @JohnyBeGood on GitHub (May 20, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Karakeep ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/karakeep.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📝 Provide a clear and concise description of the issue. Unable to install inside the Proxmox. ### 🔄 Steps to reproduce the issue. Start either standard or advanced install. It will show an error at the end (/dev/fd/63: line 73: SPINNER_PID: unbound variable) and complain there is no network. Even though the error is shown, it creates the container. At one point I had few of them running. Updated Proxmox and rebooted, made sure there was a network connection. It does not make any difference. ### ❌ Paste the full error output (if available). __ __ / /______ __________ _/ /_____ ___ ____ / //_/ __ `/ ___/ __ `/ //_/ _ \/ _ \/ __ \ / ,< / /_/ / / / /_/ / ,< / __/ __/ /_/ / /_/|_|\__,_/_/ \__,_/_/|_|\___/\___/ .___/ /_/ 🧩 Using Advanced Settings on node pve-main 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 🔐 Root Password: ******** 🆔 Container ID: 128 🏠 Hostname: karakeep 💾 Disk Size: 20 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 4096 MiB 🌉 Bridge: vmbr0 📡 IP Address: dhcp 🌐 Gateway IP Address: Default 📡 APT-Cacher IP Address: Default 🚫 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 🔍 Verbose Mode: yes 🚀 Creating a karakeep LXC using the above advanced settings ✔️ Using local for Template Storage. ✔️ Using local-zfs for Container Storage. ✔️ Updated LXC Template List ✔️ LXC Template is ready to use. ✔️ LXC Container 128 was successfully created. ✔️ Started LXC Container net.ipv6.conf.all.disable_ipv6 = 1 ⠹ ✖️ No Network! ner OS ✖️ No Network After 10 Tries 📡 Check Network Settings /dev/fd/63: line 73: SPINNER_PID: unbound variable root@pve-main:~# ### 🖼️ Additional context (optional). Did another advanced install with verbose: __ __ / /______ __________ _/ /_____ ___ ____ / //_/ __ `/ ___/ __ `/ //_/ _ \/ _ \/ __ \ / ,< / /_/ / / / /_/ / ,< / __/ __/ /_/ / /_/|_|\__,_/_/ \__,_/_/|_|\___/\___/ .___/ /_/ 🧩 Using Advanced Settings on node pve-main 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 🔐 Root Password: ******** 🆔 Container ID: 125 🏠 Hostname: karakeep 💾 Disk Size: 20 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 4096 MiB 🌉 Bridge: vmbr0 📡 IP Address: dhcp 🌐 Gateway IP Address: Default 📡 APT-Cacher IP Address: Default 🚫 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 🔍 Verbose Mode: yes 🚀 Creating a karakeep LXC using the above advanced settings ✔️ Using local for Template Storage. ✔️ Using local-zfs for Container Storage. ✔️ Updated LXC Template List ✔️ LXC Template is ready to use. ✔️ LXC Container 125 was successfully created. ✔️ Started LXC Container net.ipv6.conf.all.disable_ipv6 = 1 ⠹ ✖️ No Network! ner OS ✖️ No Network After 10 Tries 📡 Check Network Settings /dev/fd/63: line 73: SPINNER_PID: unbound variable root@pve-main:~# _No response_
OVERLORD added the bug label 2026-02-04 22:25:26 +03:00
OVERLORD commented 2026-02-04 22:25:32 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (May 20, 2025):

You have issues with your network, wich is not a Script issue.
Please check your PVE Node settings that vmbr0 has access to a DHCP server.
Or test by giving the container a fixed IP Address during advanced install.

@michelroegl-brunner commented on GitHub (May 20, 2025): You have issues with your network, wich is not a Script issue. Please check your PVE Node settings that vmbr0 has access to a DHCP server. Or test by giving the container a fixed IP Address during advanced install.
OVERLORD commented 2026-02-04 22:25:39 +03:00
Author
Owner
Copy Link

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

You dont get an IP/hostname inside the LXC. The node does not matter in this case. It happens at runtime in the LXC itself. This either receives no IP or no host name from the DHCP.

@MickLesk commented on GitHub (May 20, 2025): You dont get an IP/hostname inside the LXC. The node does not matter in this case. It happens at runtime in the LXC itself. This either receives no IP or no host name from the DHCP.
OVERLORD commented 2026-02-04 22:25:44 +03:00
Author
Owner
Copy Link

@JohnyBeGood commented on GitHub (May 20, 2025):

Thanks for taking the time to reply!

So, I narrowed it down. It turns out Adguard on my OPNsense is blocking some of the domains. My guess is github as I'm not sure what other urls script is downloading from during the install. I added this to my custom filter rules.
@@||github.com^ @@||raw.githubusercontent.com^ @@||deb.debian.org^ @@||security.debian.org^ @@||archive.ubuntu.com^ @@||download.proxmox.com^
Still testing to see if that solves the issue and will report back. Posting this to help others.

This is a temporary fix:

Image
@JohnyBeGood commented on GitHub (May 20, 2025): Thanks for taking the time to reply! So, I narrowed it down. It turns out Adguard on my OPNsense is blocking some of the domains. My guess is github as I'm not sure what other urls script is downloading from during the install. I added this to my custom filter rules. `@@||github.com^ @@||raw.githubusercontent.com^ @@||deb.debian.org^ @@||security.debian.org^ @@||archive.ubuntu.com^ @@||download.proxmox.com^ ` Still testing to see if that solves the issue and will report back. Posting this to help others. This is a temporary fix: <img width="673" alt="Image" src="https://github.com/user-attachments/assets/e4c3a380-79eb-49e4-8174-f40073046769" />
OVERLORD commented 2026-02-04 22:25:47 +03:00
Author
Owner
Copy Link

@JohnyBeGood commented on GitHub (May 20, 2025):

Just is case someone runs into the same issue. Adding custom rules above did not help. Adding Google DNS as a secondary DNS in Proxmox solved the issue.

Image
@JohnyBeGood commented on GitHub (May 20, 2025): Just is case someone runs into the same issue. Adding custom rules above did not help. Adding Google DNS as a secondary DNS in Proxmox solved the issue. <img width="356" alt="Image" src="https://github.com/user-attachments/assets/24ecae59-af99-4a6c-8ad8-c6ef862dd3c8" />
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
question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
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#987
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?