-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DHCP Discovery - Operation not permitted #62188
Comments
dhcp documentation |
Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration ( |
Could you provide information on how you run this container, so we can reroduce it? |
Sure, also i've found the issue... it's not directly related to HA Because i don't think this is a "supported" setup, i guess we can close this issue. |
I've managed to solve this. Thanks a lot for your work and sorry for taking your time. |
Hi @bserrao Can you share the config you used to deploy the container in Podman after figuring out the above? I assume since you removed host networking you now have a port mapping for at least 8123? |
Hey there @JHBoricua, sure...
|
This seems to have been true even for earlier home-assistant containers, and probably crept in as a change by Redhat to improve podman security vis-a-viz docker in terms of limiting container capabilities. To make this work for myself, podman needs CAP_NET_RAW (basically DHCP Discovery/Inspection is running a sniffer on the network, hence the RAW). This seems to be true even for rooted containers (had thought it only applied to rootless). Either -p or host doesn't change whether discovery works. CAP_NET_BIND_SERVICE only affects if listening below port 1000, I believe, so the minimum change is to add this stanza:
|
Sadly even after adding CAP_NET_RAW and CAP_NET_BIND_SERVICE it still throws the error message |
@JHBoricua when I experienced this, it was because I hadn't deleted the old container. |
The problem
I'm seeing this error (
Cannot watch for dhcp packets: [Errno 1] Operation not permitted
) in home assistant log. As a result some integrations that rely on this don't work properly.I'm running a Home Assistant container on Fedora Coreos and i've already disabled SELinux.
Any clue why is this happening?
What version of Home Assistant Core has the issue?
core-2021.12.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
DHCP Discovery
Link to integration documentation on our website
https://www.home-assistant.io/integrations/dhcp
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: