HostResolver shouldn't return IPv6 addresses by default #547
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
They don't work over the SLIRP interface, and sometimes don't even work over a bridged vmnet interface.
See also rancher-sandbox/rancher-desktop#1193
This PR deprecates the
useHostResolver
setting and replaces it withhostResolver.enabled
. The old setting can still be used, but if the new property is set, any old setting in the same file is being ignored. Generating proper warnings gets pretty complex when the interaction betweendefault.yaml
,lima.yaml
, andoverride.yaml
have to be considered.It could be argued that
HostResolver.LookupIPv6
should default totrue
for compatibility with previous releases. However, given that it seems to be broken in some setups, disabling IPv6 by default seems like a safer choice to me.Also includes one bug fix for
limactl debug dns 5533 5533
, which previously ignored the TCP port.Aside: I needed to include the TCP port during testing because
limactl debug dns 5533
(without-6
) option resulted in: