Can I Use Host Network Mode for Home Assistant and Still Connect Caddy?

Have you noticed any devices that won't function with this setup? I was concerned about using my router integration for connected devices. I did manage to get my Caddy configuration working with a bit of tweaking—check out this link for some tips!

Here's how I set up Home Assistant to be reverse proxied by Caddy without using host networking. I just put all my containers in the same Docker network:
```yaml
homeassistant:
image: homeassistant/home-assistant:stable
restart: unless-stopped
environment:
- TZ:${TZ}
volumes:
- $BASE_PATH/homeassistant:/config
networks:
- homeassistant-net
- caddy
```

It works well as long as everything is in the same network!

Since Docker defaults to `network_mode: bridge`, it isolates containers from the host network. This means Home Assistant won't be able to discover devices on the LAN unless it uses the host's network stack. If you go with `network_mode: host`, it could solve the discovery issue, but consider if that’s the best approach for your setup.

To wrap your head around this, it's important to understand how network namespaces work. Using `network_mode: host` means that Home Assistant's container runs directly in the host's network namespace. For Caddy to communicate with it, you'd essentially need to bridge it to the host's network, which complicates things since containers are usually isolated in their own namespaces. Still, Caddy can proxy to software running on the host, but you may need to tweak your Caddy configuration a bit to get it right.

Just a heads up! Some folks from the Home Assistant community recommend running it as a full Virtual Machine or on bare metal instead of in a container. They say it tends to be more reliable. You can find more info on that on their installation page.