starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 09:15:59 +03:00

[GH-ISSUE #6324] Pihole NTP warning #1355

New issue

Closed

opened 2026-02-26 12:48:36 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 12:48:36 +03:00

Owner

Originally created by @jabofh on GitHub (Jul 28, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/6324

Please verify that you have read and understood the guidelines.

yes

What type of issue is this?

Documentation

A clear and concise description of the issue.

We should probably have another warning in the JSON documentation for Pihole.

When you install the Pihole LXD container you should install it as a privileged container if you want to use it as a NTP server.

If you don't you may well run into issues with it being deemed an "unusable" server and getting ignored by Linux nodes, and have your nodes experiencing time drift.

Which browser are you using?

Other

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

No response

Please provide detailed steps to reproduce the issue.

No response

Originally created by @jabofh on GitHub (Jul 28, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/6324 ### Please verify that you have read and understood the guidelines. yes ### What type of issue is this? Documentation ### A clear and concise description of the issue. We should probably have another warning in the JSON documentation for Pihole. When you install the Pihole LXD container you should install it as a privileged container _if_ you want to use it as a NTP server. If you don't you may well run into issues with it being deemed an "unusable" server and getting ignored by Linux nodes, and have your nodes experiencing time drift. ### Which browser are you using? Other ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. _No response_ ### Please provide detailed steps to reproduce the issue. _No response_

kerem

2026-02-26 12:48:36 +03:00

closed this issue
added the
website
label

kerem commented

2026-02-26 12:48:37 +03:00

Author

Owner

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

running Pi-hole in a privileged LXC? Bad idea, mate. You're basically giving it root access to your entire host — one slip-up or exploit, and boom, your whole server's toast. Stick to unprivileged containers unless you wanna roll the dice with your network's safety. It's like leaving your front door wide open 'cause the mailman needs to drop a letter. Only for useless ntp.

@MickLesk commented on GitHub (Jul 28, 2025): running Pi-hole in a privileged LXC? Bad idea, mate. You're basically giving it root access to your entire host — one slip-up or exploit, and boom, your whole server's toast. Stick to unprivileged containers unless you wanna roll the dice with your network's safety. It's like leaving your front door wide open 'cause the mailman needs to drop a letter. Only for useless ntp.

kerem commented

2026-02-26 12:48:37 +03:00

Author

Owner

@jabofh commented on GitHub (Jul 29, 2025):

Unfortunately NTP is both useful and quite important in my environment. To mitigate the risk of running the LXC container privileged I have my Proxmox node hidden away behind two discrete firewalls, with only me having direct access to it.

Bearing in mind that NTP is important to me, and I'm already using Pihole, which already runs as an NTP server, this seemed the most expedient.

@jabofh commented on GitHub (Jul 29, 2025): Unfortunately NTP is both useful and quite important in my environment. To mitigate the risk of running the LXC container privileged I have my Proxmox node hidden away behind two discrete firewalls, with only me having direct access to it. Bearing in mind that NTP _is_ important to me, and I'm already using Pihole, which already runs as an NTP server, this seemed the most expedient.

kerem commented

2026-02-26 12:48:37 +03:00

Author

Owner

@MickLesk commented on GitHub (Jul 29, 2025):

Then it would make sense from a security perspective to migrate it to a Debian or Ubuntu VM rather than an open LXC.

@MickLesk commented on GitHub (Jul 29, 2025): Then it would make sense from a security perspective to migrate it to a Debian or Ubuntu VM rather than an open LXC.

kerem referenced this issue

2026-02-26 13:32:30 +03:00

[PR #1355] [CLOSED] Revert "Install/update ActualBudget based on releases, not latest master" #3128

kerem referenced this issue

2026-02-26 13:32:33 +03:00

[PR #1376] [MERGED] Fix: ActualBudget Update-Function #3139

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#1355

No description provided.

Rows
Columns