Using host networking causes zeroconf and default_config errors

aristosv · February 22, 2022, 12:24pm

If I install home assistant using this command everything works just fine

docker pull homeassistant/home-assistant:stable
docker run -d \
 --restart=always \
 --name=homeassistant \
 -h homeassistant \
 -e PUID=1001 \
 -e PGID=1001 \
 -e TZ=Europe/Nicosia \
 --net=network \
 -p 8123:8123 \
 -v homeassistant:/config \
 homeassistant/home-assistant:stable

If I install home assistant using this command

docker pull homeassistant/home-assistant:stable
docker run -d \
 --restart=always \
 --name=homeassistant \
 -h homeassistant \
 -e PUID=1001 \
 -e PGID=1001 \
 -e TZ=Europe/Nicosia \
 --net=host \
 -v homeassistant:/config \
 homeassistant/home-assistant:stable

I get this error

and these are the logs

As you can see the only thing that changed is the networking, that is now using “host” instead of “8123” port.

These are clean installations.

What could be the issue here?

aristosv · February 22, 2022, 12:38pm

I also tried this, because I have a plex container running also but it didn’t fix the issue. I unmapped port 1900 from plex but no luck.

github.com/home-assistant/core

Auto Discovery doesn’t work | SSPD: Failed to setup listener for 0.0.0.0: [Errno 98] Address in use

opened 03:44PM - 13 Dec 21 UTC

closed 04:04PM - 14 Dec 21 UTC

exetico

integration: discovery

### The problem The core are complaining about the port for SSPD (Auto Discov…ery) are already in use. The logger are simply throwing the following error: ``` Logger: homeassistant.components.ssdp Source: components/ssdp/__init__.py:354 Integration: Simple Service Discovery Protocol (SSDP) (documentation, issues) First occurred: 12:29:55 PM (1 occurrences) Last logged: 12:29:55 PM Failed to setup listener for 0.0.0.0: [Errno 98] Address in use ``` ### What version of Home Assistant Core has the issue? core-2021.11.5 ### 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 Auto Discovery ### Link to integration documentation on our website https://www.home-assistant.io/integrations/discovery/ ### Example YAML snippet ```yaml Use the normal YAML for discovery. My setup are stock - with no special things. ``` ### Anything in the logs that might be useful for us? #### Home Assistant are already using the :5353 port The wierd thing is, that Home Assistant are already the container, which are using the `:5959` port, if I'm correct. Here's an output, while the HA-instance are running: ```log > sudo lsof -i :5353 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME python3 21432 root 13u IPv4 116981 0t0 UDP *:mdns python3 21432 root 22u IPv4 117012 0t0 UDP localhost:mdns python3 21432 root 24u IPv4 117013 0t0 UDP 10.0.0.5:mdns python3 21432 root 25u IPv4 117014 0t0 UDP 10.0.0.109:mdns python3 21432 root 26u IPv4 117015 0t0 UDP 172.17.0.1:mdns python3 21432 root 27u IPv4 117016 0t0 UDP 172.19.0.1:mdns ``` And here's the result, if I kill the HA-instance: ``` > sudo lsof -i :5353 ... nothing ... ``` The HA- instance is in "host" network-mode, and has been working like this for yeas. The instance had not been updated for half a year (_due to a stupid mistake, in my script_), so I'm unsure if something related configuration-changes, has something to do with it. By looking at the `PID`, it's clear that the python-script for Home Assistant are the one using `:5353`: ``` > top -c | grep 21432 21432 root 20 0 457784 351572 31196 S 0.7 6.9 0:23.10 python3 -m homeassistant --config /config ``` **Am I looking at the wrong things, while trying to spot the actual issue?** I'm running: `Home Assistant 2021.11.5` With `Frontend version: 20211109.0 - latest` In a docker-container on Debian The outputs are from the host-system, not within the instance/container. Could it be something related to another module? ### Additional information I posted it within the forum, before submitting this issue. Two other persons are facing the same issue - so I guess it's more than that. [Find the thread here](https://community.home-assistant.io/t/auto-discovery-doesnt-work-sspd-failed-to-setup-listener-for-0-0-0-0-errno-98-address-in-use/360848). EDIT: Huh. Formatting was very odd... Fixed.

aristosv · February 22, 2022, 1:28pm

it seems I also had to unmap port 5353 on plex. Now home assistant is ok.