Replies: 1 comment 1 reply
-
|
So there are a couple differences using the MDNS container vs changing just the hostname
The I think we can go either way for sure, as long as we know that there might be a potentially more bumpy experience using either the |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Considering the size and complexity of the MDNS container, and the fact that it isn't going to be needed by a lot of users, is it worth switching it out for the hostname container (https://github.com/balenablocks/hostname) as the default, and then let users add the MDNS if they require it? The hostname container will change the hostname to a specified name, which will then make the device accessible via
the-specified-name.local. The only reason for then needing an additional MDNS is if that hostname is going to be changing, which is quite a niche use case.Hostname container is around 10mb and MDNS is 200mb+. It is also uses less resources and exits when finished.
@nucleardreamer
Beta Was this translation helpful? Give feedback.
All reactions