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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks ok to me but it may be a more general solution to deal with distributions running
systemd-resolved
; why limit it to just Flatcar?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At least in my environment (Flatcar Linux) this inevitably became a problem.
I've been tracking this issue steadily until very recently, and found that it crashes when the `nodelocaldns' feature is enabled.
I don't think this works the same on other distributions (such as Ubuntu). The
enable_nodelocaldns
feature is already enabled by default, so I know that no other major distributions have reported problems with it.Another peculiarity is that, at least in Flatcar Linux, the
/etc/resolv.conf
configuration file is not valid, and instead depends only on thesystemd-resolved
. However, there are severalresolvconf
stuffs that are specific toFlatcar Linux
, but I still don't know why they exist.Especially,
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, ok, lets go ahead with this change then and see if other deployments report this problem, I have a suspicion that ubuntu 22.04 may be affected as well bug since I'm not running that in production anywhere this is just a suspicion.