Open moritz89 opened 6 years ago
In the case of using the image in a multi-docker environment (docker-compose), it is necessary to specify the dbus label to expose its interface. Would it make sense to add it in this example? The following docker-compose setup works:
version: '2' services: avahi: build: ./avahi container_name: avahi privileged: true labels: io.resin.features.dbus: '1'
The relevant documentation is available on the multicontainer pages. The directory was reorganized to be a subfolder:
root-folder - docker-compose.yml - avahi - Dockerfile.template - myserver.py - README.md - requirements.txt - start.sh - avahi - __init__.py - server.py - service.py
Related question, why does Avahi not work when the flask component is removed?
In the case of using the image in a multi-docker environment (docker-compose), it is necessary to specify the dbus label to expose its interface. Would it make sense to add it in this example? The following docker-compose setup works:
The relevant documentation is available on the multicontainer pages. The directory was reorganized to be a subfolder: