Docker container stops with the error ExceptionHandler: EAFNOSUPPORT, Address family not supported by protocol
Closed this issue · 6 comments
I have followed the guiance at https://www.room-assistant.io/guide/quickstart-docker.html. The container stops with the error "ExceptionHandler: EAFNOSUPPORT, Address family not supported by protocol":
| date | stream | content |
|---|---|---|
| 2021-04-13 08:08:27 | stdout | 4/13/2021, 8:08:27 AM - �[31merror�[39m - ExceptionHandler: EAFNOSUPPORT, Address family not supported by protocol |
| 2021-04-13 08:08:27 | stdout | 4/13/2021, 8:08:27 AM - �[32minfo�[39m - NestFactory: Starting Nest application... |
| 2021-04-13 08:08:26 | stdout | 4/13/2021, 8:08:26 AM - �[32minfo�[39m - IntegrationsModule: Loading integrations: bluetooth-classic, home-assistant |
| 2021-04-13 08:08:25 | stdout | *** WARNING *** For more information see http://0pointer.de/blog/projects/avahi-compat.html |
| 2021-04-13 08:08:25 | stdout | *** WARNING *** Please fix your application to use the native API of Avahi! |
| 2021-04-13 08:08:25 | stdout | *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi. |
| 2021-04-13 08:08:25 | stdout | *** WARNING *** For more information see http://0pointer.de/blog/projects/avahi-compat.html |
| 2021-04-13 08:08:25 | stdout | *** WARNING *** Please fix your application to use the native API of Avahi! |
| 2021-04-13 08:08:25 | stdout | *** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi. |
The error occurs straight after adding bluetoothClassic integration. Configuration file is attached (I renamed it to .txt)
local.yml.txt
Do you have an IPv6 only network somewhere? Either in the Docker environment or on the host. room-assistant atm only really works on IPv4 for a few reasons, so I'd expect the error to come from that. Shouldn't have anything to do with the bluetoothClassic integration though.
Does the container start fine if you disable bluetoothClassic temporarily? If so, double check that the Bluetooth adapter is available on the host & that you are running the container with host networking.
Yes, the container runs without bluetooth
In that case the issue is that the container can't access the Bluetooth adapter properly. Note the extra requirements for Docker mentioned in the BT Classic docs.
Thanks