Unbound Installation in PiHole Script failed #2322

Closed
opened 2026-02-05 04:29:01 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @kharas80 on GitHub (Jan 14, 2026).

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?

PiHole

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

9.1.4

📝 Provide a clear and concise description of the issue.

PiHole installation started with default settings. Errors occur during unbound installation. See below for screen output, log file, and steps.

🔄 Steps to reproduce the issue.

Default Install
https://install.pi-hole.net -> yes
with unbound -> yes
unbound recursive -> yes

Paste the full error output (if available).

Screen output (logfile below)
    ____  _ __          __   
   / __ \(_) /_  ____  / /__ 
  / /_/ / / __ \/ __ \/ / _ \
 / ____/ / / / / /_/ / /  __/
/_/   /_/_/ /_/\____/_/\___/ 
                             
  ⚙️  Using Default Settings on node jupiter2
  💡  PVE Version 9.1.4 (Kernel: 6.17.4-2-pve)
  🆔  Container ID: 125
  🖥️  Operating System: debian (13)
  📦  Container Type: Unprivileged
  💾  Disk Size: 2 GB
  🧠  CPU Cores: 1
  🛠️  RAM Size: 512 MiB
  🚀  Creating a Pihole LXC using the above default settings
  
  ✔️   Storage local (Free: 3.5TB  Used: 242.0MB) [Template]
  ✔️   Storage local-zfs (Free: 3.5TB  Used: 45.6GB) [Container]
  ✔️   Storage 'local-zfs' (zfspool) validated
  ✔️   Template storage 'local' validated
  ✔️   Template search completed
  ✔️   Template debian-13-standard_13.1-2_amd64.tar.zst [local]
  ✔️   LXC Container 125 was successfully created.
  ✔️   Started LXC Container
  ✔️   Network in LXC is reachable (ping)
  ✔️   Customized LXC Container
  ✔️   Set up Container OS
  ✔️   Network Connected: 192.168.188.124 fd9b:f9a1:e5fe:e9b1:be24:11ff:fe8e:1747 2003:e7:f04:9000:be24:11ff:fe8e:1747 
  ✔️   IPv4 Internet Connected
  ✔️   IPv6 Internet Connected
  ✔️   Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )
  ✔️   Updated Container OS
  💡   WARNING: This script will run an external installer from a third-party source (https://pi-hole.net/).
  💡   The following code is NOT maintained or audited by our repository.
  💡   If you have any doubts or concerns, please review the installer code before proceeding:
         🌐   →  https://install.pi-hole.net

      Do you want to continue? [y/N]: y
  ✔️   Installed Dependencies
  ✔️   Installed Pi-hole
      Would you like to add Unbound? <y/N> y
      Unbound is configured as a recursive DNS server by default, would you like it to be configured as a forwarding DNS server (using DNS-over-TLS (DoT)) instead? <y/N> N
  ✖️   in line 152: exit code 1 (General error / Operation not permitted): while executing command systemctl enable -q --now unbound
--- Last 20 lines of silent log ---
Preparing to unpack .../libevent-2.1-7t64_2.1.12-stable-10+b1_amd64.deb ...
Unpacking libevent-2.1-7t64:amd64 (2.1.12-stable-10+b1) ...
Selecting previously unselected package libhiredis1.1.0:amd64.
Preparing to unpack .../libhiredis1.1.0_1.2.0-6+b3_amd64.deb ...
Unpacking libhiredis1.1.0:amd64 (1.2.0-6+b3) ...
Selecting previously unselected package libpython3.13:amd64.
Preparing to unpack .../libpython3.13_3.13.5-2_amd64.deb ...
Unpacking libpython3.13:amd64 (3.13.5-2) ...
Selecting previously unselected package unbound.
Preparing to unpack .../unbound_1.22.0-2+deb13u1_amd64.deb ...
Unpacking unbound (1.22.0-2+deb13u1) ...
Setting up libpython3.13:amd64 (3.13.5-2) ...
Setting up libevent-2.1-7t64:amd64 (2.1.12-stable-10+b1) ...
Setting up libhiredis1.1.0:amd64 (1.2.0-6+b3) ...
Setting up unbound (1.22.0-2+deb13u1) ...
Created symlink '/etc/systemd/system/multi-user.target.wants/unbound.service' → '/usr/lib/systemd/system/unbound.service'.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 148.
Created symlink '/etc/systemd/system/unbound.service.wants/unbound-resolvconf.service' → '/usr/lib/systemd/system/unbound-resolvconf.service'.
Processing triggers for man-db (2.13.1-1) ...
Processing triggers for libc-bin (2.41-12+deb13u1) ...
-----------------------------------
 📋 Log saved to: /root/.install-96d424a3.log
  ✖️   Installation failed in container 125 (exit code: 1)

✔ Installation log: /tmp/install-lxc-125-96d424a3.log

Remove broken container 125? (Y/n) [auto-remove in 60s]: 

[install-lxc-125-96d424a3.log](https://github.com/user-attachments/files/24609084/install-lxc-125-96d424a3.log)

🖼️ Additional context (optional).

No response

Originally created by @kharas80 on GitHub (Jan 14, 2026). ### ✅ 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? PiHole ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/pihole.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 9.1.4 ### 📝 Provide a clear and concise description of the issue. PiHole installation started with default settings. Errors occur during unbound installation. See below for screen output, log file, and steps. ### 🔄 Steps to reproduce the issue. Default Install https://install.pi-hole.net -> yes with unbound -> yes unbound recursive -> yes ### ❌ Paste the full error output (if available). ``` Screen output (logfile below) ____ _ __ __ / __ \(_) /_ ____ / /__ / /_/ / / __ \/ __ \/ / _ \ / ____/ / / / / /_/ / / __/ /_/ /_/_/ /_/\____/_/\___/ ⚙️ Using Default Settings on node jupiter2 💡 PVE Version 9.1.4 (Kernel: 6.17.4-2-pve) 🆔 Container ID: 125 🖥️ Operating System: debian (13) 📦 Container Type: Unprivileged 💾 Disk Size: 2 GB 🧠 CPU Cores: 1 🛠️ RAM Size: 512 MiB 🚀 Creating a Pihole LXC using the above default settings ✔️ Storage local (Free: 3.5TB Used: 242.0MB) [Template] ✔️ Storage local-zfs (Free: 3.5TB Used: 45.6GB) [Container] ✔️ Storage 'local-zfs' (zfspool) validated ✔️ Template storage 'local' validated ✔️ Template search completed ✔️ Template debian-13-standard_13.1-2_amd64.tar.zst [local] ✔️ LXC Container 125 was successfully created. ✔️ Started LXC Container ✔️ Network in LXC is reachable (ping) ✔️ Customized LXC Container ✔️ Set up Container OS ✔️ Network Connected: 192.168.188.124 fd9b:f9a1:e5fe:e9b1:be24:11ff:fe8e:1747 2003:e7:f04:9000:be24:11ff:fe8e:1747 ✔️ IPv4 Internet Connected ✔️ IPv6 Internet Connected ✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ ) ✔️ Updated Container OS 💡 WARNING: This script will run an external installer from a third-party source (https://pi-hole.net/). 💡 The following code is NOT maintained or audited by our repository. 💡 If you have any doubts or concerns, please review the installer code before proceeding: 🌐 → https://install.pi-hole.net Do you want to continue? [y/N]: y ✔️ Installed Dependencies ✔️ Installed Pi-hole Would you like to add Unbound? <y/N> y Unbound is configured as a recursive DNS server by default, would you like it to be configured as a forwarding DNS server (using DNS-over-TLS (DoT)) instead? <y/N> N ✖️ in line 152: exit code 1 (General error / Operation not permitted): while executing command systemctl enable -q --now unbound --- Last 20 lines of silent log --- Preparing to unpack .../libevent-2.1-7t64_2.1.12-stable-10+b1_amd64.deb ... Unpacking libevent-2.1-7t64:amd64 (2.1.12-stable-10+b1) ... Selecting previously unselected package libhiredis1.1.0:amd64. Preparing to unpack .../libhiredis1.1.0_1.2.0-6+b3_amd64.deb ... Unpacking libhiredis1.1.0:amd64 (1.2.0-6+b3) ... Selecting previously unselected package libpython3.13:amd64. Preparing to unpack .../libpython3.13_3.13.5-2_amd64.deb ... Unpacking libpython3.13:amd64 (3.13.5-2) ... Selecting previously unselected package unbound. Preparing to unpack .../unbound_1.22.0-2+deb13u1_amd64.deb ... Unpacking unbound (1.22.0-2+deb13u1) ... Setting up libpython3.13:amd64 (3.13.5-2) ... Setting up libevent-2.1-7t64:amd64 (2.1.12-stable-10+b1) ... Setting up libhiredis1.1.0:amd64 (1.2.0-6+b3) ... Setting up unbound (1.22.0-2+deb13u1) ... Created symlink '/etc/systemd/system/multi-user.target.wants/unbound.service' → '/usr/lib/systemd/system/unbound.service'. Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 148. Created symlink '/etc/systemd/system/unbound.service.wants/unbound-resolvconf.service' → '/usr/lib/systemd/system/unbound-resolvconf.service'. Processing triggers for man-db (2.13.1-1) ... Processing triggers for libc-bin (2.41-12+deb13u1) ... ----------------------------------- 📋 Log saved to: /root/.install-96d424a3.log ✖️ Installation failed in container 125 (exit code: 1) ✔ Installation log: /tmp/install-lxc-125-96d424a3.log Remove broken container 125? (Y/n) [auto-remove in 60s]: [install-lxc-125-96d424a3.log](https://github.com/user-attachments/files/24609084/install-lxc-125-96d424a3.log) ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 04:29:01 +03:00
Author
Owner

@ramonfloriano commented on GitHub (Jan 15, 2026):

Same here!

in line 152: exit code 1 (General error / Operation not permitted): while executing command systemctl enable -q --now unbound

Image
@ramonfloriano commented on GitHub (Jan 15, 2026): Same here! _in line 152: exit code 1 (General error / Operation not permitted): while executing command systemctl enable -q --now unbound_ <img width="1382" height="457" alt="Image" src="https://github.com/user-attachments/assets/dab7e91f-04a0-4e01-b44a-8b2f8ed99b71" />
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2322