Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix dns resolution in base image #6

Closed
richardcase opened this issue Jan 7, 2022 · 0 comments · Fixed by weaveworks-liquidmetal/cluster-api-provider-microvm#81
Closed

Comments

@richardcase
Copy link
Contributor

With our current base image we have issues with DNS resolution. Our base image is using systemd/systemd-resolvd and this requires that /etc/resolv.conf be symlinked to /run/systemd/resolve/stub-resolv.conf . However, when using docker/buildkit/kaniko its not possible to make changes to resolv.conf as this is treated specially.

We are working around this issue temporarily by using bootcmd in cloud-init to run ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf when flintlock is called from capmvm.

However, we need a long term solution where the container image is setup correctly for dns resolution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Closed
Development

Successfully merging a pull request may close this issue.

1 participant