Debian 13 LXC Advanced Settings install fails #1891

Closed
opened 2026-02-05 02:40:26 +03:00 by OVERLORD · 4 comments
Owner

Originally created by @NorbertHD on GitHub (Oct 28, 2025).

Have you read and understood the above guidelines?

yes

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

Debian LXC

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/8.4.14/b502d23c55afcba1 (running kernel: 6.8.12-15-pve)

📝 Provide a clear and concise description of the issue.

When installing with default settings all is okay.
But with Advanced Settings (because I need privileged) the installation fails with error:

[ERROR] in line 555: exit code 0: while executing command BRIDGES=$(echo "$BRIDGES" | grep -v '^\s*$' | sort | uniq)

🔄 Steps to reproduce the issue.

  1. Execute bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/debian.sh)"
  2. Choose Advanced Settings
  3. Enter the settings
  4. Script exits with error

Paste the full error output (if available).

🧩 Using Advanced Settings on node pve
🖥️ Operating System: debian
🌟 Version: 13
📦 Container Type: Privileged
🔐 Root Password: Automatic Login
🆔 Container ID: 109
🏠 Hostname: test
💾 Disk Size: 4 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 2048 MiB

[ERROR] in line 555: exit code 0: while executing command BRIDGES=$(echo "$BRIDGES" | grep -v '^\s*$' | sort | uniq)

🖼️ Additional context (optional).

No response

Originally created by @NorbertHD on GitHub (Oct 28, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Debian LXC ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/debian.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/8.4.14/b502d23c55afcba1 (running kernel: 6.8.12-15-pve) ### 📝 Provide a clear and concise description of the issue. When installing with default settings all is okay. But with Advanced Settings (because I need privileged) the installation fails with error: [ERROR] in line 555: exit code 0: while executing command BRIDGES=$(echo "$BRIDGES" | grep -v '^\s*$' | sort | uniq) ### 🔄 Steps to reproduce the issue. 1. Execute bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/debian.sh)" 2. Choose Advanced Settings 3. Enter the settings 4. Script exits with error ### ❌ Paste the full error output (if available). 🧩 Using Advanced Settings on node pve 🖥️ Operating System: debian 🌟 Version: 13 📦 Container Type: Privileged 🔐 Root Password: Automatic Login 🆔 Container ID: 109 🏠 Hostname: test 💾 Disk Size: 4 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB [ERROR] in line 555: exit code 0: while executing command BRIDGES=$(echo "$BRIDGES" | grep -v '^\s*$' | sort | uniq) ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 02:40:26 +03:00
Author
Owner

@MickLesk commented on GitHub (Oct 28, 2025):

And what are your Bridges?

@MickLesk commented on GitHub (Oct 28, 2025): And what are your Bridges?
Author
Owner

@NorbertHD commented on GitHub (Oct 28, 2025):

And what are your Bridges?

Where do I look?

echo "$BRIDGES" gives nothing.

@NorbertHD commented on GitHub (Oct 28, 2025): > And what are your Bridges? Where do I look? echo "$BRIDGES" gives nothing.
Author
Owner

@MickLesk commented on GitHub (Oct 28, 2025):

Datacenter -> Node -> Network

@MickLesk commented on GitHub (Oct 28, 2025): Datacenter -> Node -> Network
Author
Owner

@NorbertHD commented on GitHub (Oct 28, 2025):

Ah, thank you. There is no bridge. Now I know what's going on. After a BIOS update the network configuration with ifupdown2 was broken. So I made a manual /etc/network/interfaces file. Seems that I have made an error there or it's not the correct way.
Anyway, it's time for a fresh proxmox 9.

@NorbertHD commented on GitHub (Oct 28, 2025): Ah, thank you. There is no bridge. Now I know what's going on. After a BIOS update the network configuration with ifupdown2 was broken. So I made a manual /etc/network/interfaces file. Seems that I have made an error there or it's not the correct way. Anyway, it's time for a fresh proxmox 9.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1891