Avahi as mDNS Advertiser (in Docker) Prevents Zigbee2MQTT Container from Starting
### Analysis

Running Homebridge in Docker using Avahi, configured as per instructions here (https://github.com/homebridge/homebridge/wiki/mDNS-Options#avahi-linux-and-docker) prevents Zigbee2MQTT container from starting. Zigbee2MQTT is one of the most popular implementations for connecting Zigbee devices to Homebridge.

Mounting files as per linked instructions causes issues:
```
volumes:
      - /var/run/dbus:/var/run/dbus
      - /var/run/avahi-daemon/socket:/var/run/avahi-daemon/socket
```

Un-mounting these gets everything back to normal.

Zigbee2MQTT container can be run first and Homebridge second - then it works. If Zigbee2MQTT container tries to start after Homebridge one (running Avahi with 2 files mounted) - Docker will exit with code 1 and "unknown error"

### Expected Behavior

Homebridge and Zigbee2MQTT containers should be able to run without conflicts.

### Steps To Reproduce

1. Using default docker-compose - start Homebridge in Docker with Avahi as mDNS Advertiser and required files mounted per  https://github.com/homebridge/homebridge/wiki/mDNS-Options#avahi-linux-and-docker
2. Setup Zigbee2MQTT: https://www.zigbee2mqtt.io/guide/installation/02_docker.html#docker-compose
3. When you try `sudo docker compose up` from Zigbee2MQTT folder - it won't be able to start
4. Re-setting Homebridge back to use Ciao and removing required mounted files for Avahi solves the problem

### Logs

```markdown
N/A
```


### Configuration

```json
N/A
```


### Environment

- OS: Debian 11 (with all latest updates)
- Software: Homebridge 1.8.4
- Node: 20.17.0
- npm: 10.8.2

### Process Supervisor

Docker (Mention image name in `Additional Context`)

### Additional Context

homebridge/homebridge:latest