Fix DNS resolution in initramfs #367
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add DNS servers to /etc/resolv.conf after interfaces are setup via configure_networking
Create resolv.conf with all configured interfaces
Copy libs into initrd required for DNS resolution
sergio-correia
approved these changes
Jan 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As mentioned in #148 there seems to be a problem with the name resolution when using tang pin. If the URL to the server is not a plain IP, clevis is unable to contact tang. I could recreate this issue on Ubuntu 11. The changes in initramfs-tool hooks and scripts fixed it.
In my test setup i could only verify the changes with a DHCP server that hands out a single DNS server via IPv4 on a single interface. So the second IPv4 DNS, IPv6 DNS and multiple interfaces section in the code is only proofread and not tested.