This repository has been archived by the owner on Dec 7, 2023. It is now read-only.
Shadow the bogus /etc/resolv.conf of centos:8 to fix wksctl
#611
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.
The
centos:8
image currently used as the base forweaveworks/ignite-centos:latest
includes a bogus/etc/resolv.conf
file (that normally gets shadowed by Docker):This gets picked up by Ignite as a custom resolver configuration, so it won't be replaced with the symlink to the in-kernel DHCP at
/proc/net/pnp
. Subsequently, this then breakswksctl
integration as the Footloose-managed VMs don't have proper resolving configured resulting in no internet access (this probably affects Firekube as well).Fix this by copying a blank file over
/etc/resolv.conf
during build.