SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-22 05:52:48 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Pihole NTP warning #1585

New Issue
Closed
opened 2025-11-20 05:12:48 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 05:12:48 -05:00
Owner
Copy Link

Originally created by @jabofh on GitHub (Jul 28, 2025).

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). ### 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_
saavagebueno added the website label 2025-11-20 05:12:48 -05:00
saavagebueno commented 2025-11-20 05:12:49 -05:00
Author
Owner
Copy Link

@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.
saavagebueno commented 2025-11-20 05:12:49 -05:00
Author
Owner
Copy Link

@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.
saavagebueno commented 2025-11-20 05:12:49 -05:00
Author
Owner
Copy Link

@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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label website
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1585
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?