[GH-ISSUE #10036] DiscoPanel requires privileged docker access #2175

Closed
opened 2026-02-26 12:51:33 +03:00 by kerem · 3 comments
Owner

Originally created by @PouletteMC on GitHub (Dec 16, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10036

Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

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

DiscoPanel

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/discopanel.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/9.0.10/deb1ca707ec72a89 (running kernel: 6.14.11-2-pve)

📝 Provide a clear and concise description of the issue.

The make gen build step runs a docker container that requires more advanced docker features than what the script can do

(it worked on my machine, but not here I guess)

🔄 Steps to reproduce the issue.

Step 1: Run the discopanel install script
Step 2: Wait for it to fail

Paste the full error output (if available).

Status: Downloaded newer image for bufbuild/buf:latest
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: open sysctl net.ipv4.ip_unprivileged_port_start file: reopen fd 8: permission denied

Run 'docker run --help' for more information
make: *** [Makefile:111: proto] Error 126

🖼️ Additional context (optional).

Will create a PR to hopefully fox these issues

Originally created by @PouletteMC on GitHub (Dec 16, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/10036 ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? DiscoPanel ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/discopanel.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/9.0.10/deb1ca707ec72a89 (running kernel: 6.14.11-2-pve) ### 📝 Provide a clear and concise description of the issue. The make gen build step runs a docker container that requires more advanced docker features than what the script can do (it worked on my machine, but not here I guess) ### 🔄 Steps to reproduce the issue. Step 1: Run the discopanel install script Step 2: Wait for it to fail ### ❌ Paste the full error output (if available). Status: Downloaded newer image for bufbuild/buf:latest docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: open sysctl net.ipv4.ip_unprivileged_port_start file: reopen fd 8: permission denied Run 'docker run --help' for more information make: *** [Makefile:111: proto] Error 126 ### 🖼️ Additional context (optional). Will create a PR to hopefully fox these issues
kerem 2026-02-26 12:51:33 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@MickLesk commented on GitHub (Dec 16, 2025):

Known Docker/PVE AppArmor Bug. Update your Proxmox and Test again

<!-- gh-comment-id:3660623229 --> @MickLesk commented on GitHub (Dec 16, 2025): Known Docker/PVE AppArmor Bug. Update your Proxmox and Test again
Author
Owner

@PouletteMC commented on GitHub (Dec 16, 2025):

Proxmox should be up to date, but I'll try

<!-- gh-comment-id:3660628851 --> @PouletteMC commented on GitHub (Dec 16, 2025): Proxmox should be up to date, but I'll try
Author
Owner

@PouletteMC commented on GitHub (Dec 16, 2025):

It was indeed my proxmox not updating properly...

<!-- gh-comment-id:3660939447 --> @PouletteMC commented on GitHub (Dec 16, 2025): It was indeed my proxmox not updating properly...
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE#2175
No description provided.