Zeroconf discovery from docker-compose container to LAN host
For an IoT system there is the requirement that base stations automatically discover nearby devices, and then connect to them. The software on the base stations is deployed using docker-compose.
Services advertise using mDNS (zeroconf), and identify themselves as being of the type mytype. Clients use aiozeroconf to discover services matching _mytype._tcp.local..
The problem is that clients inside a docker-compose network don't discover services in the LAN network - even if they are otherwise reachable.
Currently, I have the following setup:
LAN (Wifi)
- IoT device
- ServiceA
- Host / base station
- ClientA
- Docker-compose network
- ServiceB
- ClientB
- ClientA finds both ServiceA and ServiceB
- ClientB finds ServiceB
- avahi-discover on Host finds both ServiceA and ServiceB
- ClientB can connect to ServiceA using the LAN IP (192.168.x.x)
Is this scenario considered out-of-spec for mDNS (ServiceA no longer considered in .local), or can this be solved?
networking docker-compose zeroconf
asked Nov 15 '18 at 10:35
KargathiaKargathia
10113
add a comment |
For an IoT system there is the requirement that base stations automatically discover nearby devices, and then connect to them. The software on the base stations is deployed using docker-compose.
Services advertise using mDNS (zeroconf), and identify themselves as being of the type mytype. Clients use aiozeroconf to discover services matching _mytype._tcp.local..
The problem is that clients inside a docker-compose network don't discover services in the LAN network - even if they are otherwise reachable.
Currently, I have the following setup:
LAN (Wifi)
- IoT device
- ServiceA
- Host / base station
- ClientA
- Docker-compose network
- ServiceB
- ClientB
- ClientA finds both ServiceA and ServiceB
- ClientB finds ServiceB
- avahi-discover on Host finds both ServiceA and ServiceB
- ClientB can connect to ServiceA using the LAN IP (192.168.x.x)
Is this scenario considered out-of-spec for mDNS (ServiceA no longer considered in .local), or can this be solved?
networking docker-compose zeroconf
asked Nov 15 '18 at 10:35
KargathiaKargathia
10113
add a comment |
For an IoT system there is the requirement that base stations automatically discover nearby devices, and then connect to them. The software on the base stations is deployed using docker-compose.
Services advertise using mDNS (zeroconf), and identify themselves as being of the type mytype. Clients use aiozeroconf to discover services matching _mytype._tcp.local..
The problem is that clients inside a docker-compose network don't discover services in the LAN network - even if they are otherwise reachable.
Currently, I have the following setup:
LAN (Wifi)
- IoT device
- ServiceA
- Host / base station
- ClientA
- Docker-compose network
- ServiceB
- ClientB
- ClientA finds both ServiceA and ServiceB
- ClientB finds ServiceB
- avahi-discover on Host finds both ServiceA and ServiceB
- ClientB can connect to ServiceA using the LAN IP (192.168.x.x)
Is this scenario considered out-of-spec for mDNS (ServiceA no longer considered in .local), or can this be solved?
networking docker-compose zeroconf
asked Nov 15 '18 at 10:35
KargathiaKargathia
10113
For an IoT system there is the requirement that base stations automatically discover nearby devices, and then connect to them. The software on the base stations is deployed using docker-compose.
Services advertise using mDNS (zeroconf), and identify themselves as being of the type mytype. Clients use aiozeroconf to discover services matching _mytype._tcp.local..
The problem is that clients inside a docker-compose network don't discover services in the LAN network - even if they are otherwise reachable.
Currently, I have the following setup:
LAN (Wifi)
- IoT device
- ServiceA
- Host / base station
- ClientA
- Docker-compose network
- ServiceB
- ClientB
- ClientA finds both ServiceA and ServiceB
- ClientB finds ServiceB
- avahi-discover on Host finds both ServiceA and ServiceB
- ClientB can connect to ServiceA using the LAN IP (192.168.x.x)
Is this scenario considered out-of-spec for mDNS (ServiceA no longer considered in .local), or can this be solved?
networking docker-compose zeroconf
networking docker-compose zeroconf
asked Nov 15 '18 at 10:35
KargathiaKargathia
10113
asked Nov 15 '18 at 10:35
KargathiaKargathia
10113
asked Nov 15 '18 at 10:35
KargathiaKargathia
10113
asked Nov 15 '18 at 10:35
KargathiaKargathia
10113
asked Nov 15 '18 at 10:35
KargathiaKargathia
10113
10113
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53317479%2fzeroconf-discovery-from-docker-compose-container-to-lan-host%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53317479%2fzeroconf-discovery-from-docker-compose-container-to-lan-host%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
