-
Notifications
You must be signed in to change notification settings - Fork 25
Avahi - daemon already running #29
Comments
I knew this was going to cause some issues... Would an environment variable help? That way, you could disable avahi selectively. |
@white-gecko do you have a better solution for this? |
@mrstegeman as far as I understand the avahi daemon is required for the webthing-arduino add-on only, right? In that case, I am ok with the environment variable solution, since I am not going to use it in the nearest feature 🤔 |
It's used for a couple things:
Neither of these are absolutely necessary, but are definitely conveniences. |
Ah yes, I can see the same message in my logs as well. But I think the avahi daemons seam not to further interfere as it seems to me. |
But sure I think an environment variable could control whether the daemon should be running. But this would not solve the issue to prevent the log messages. |
I think the issue here is that avahi is running on the host as well, and the Docker container is using host networking, so the two are somehow interfering. |
I have this log message too, and my host (CoreOS) isn't running avahi. |
My container logs are spammed with the following message:
The PID inside the container corresponds to the avahi daemon.
It has started after the upgrade from 0.9.2 version of the image (most likely after #28).
I am running the container with "network_mode: host" on Raspberry PI, which already has the avahi daemon running on the host.
Environment:
Raspberry Pi 4
Raspbian 10
Docker version 19.03.5, build 633a0ea
Image: mozillaiot/gateway:0.10.0-arm
docker-compose.yml:
The text was updated successfully, but these errors were encountered: