Skip to content
This repository was archived by the owner on May 30, 2023. It is now read-only.

Edge: coreos-base/oem-gce: Fix resolving metadata.google.internal via /etc/hosts#160

Merged
pothos merged 3 commits intoflatcar-master-edgefrom
kai/oem-gce-rkt-dns-edge
Jan 27, 2020
Merged

Edge: coreos-base/oem-gce: Fix resolving metadata.google.internal via /etc/hosts#160
pothos merged 3 commits intoflatcar-master-edgefrom
kai/oem-gce-rkt-dns-edge

Conversation

@pothos
Copy link
Copy Markdown
Contributor

@pothos pothos commented Jan 27, 2020

Ports #158 to Edge. I had to revert the replacement of rkt with Docker to apply the patch. I also think that the Docker replacement has at least missed the image name to run.

When a custom DNS server is used
coreos-metadata-sshkeys@core.service
fails to resolve metadata.google.internal
because only "metadata" is specified in /etc/hosts.
The host's /etc/nsswitch.conf is a symlink to
/usr/share/google-oslogin/nsswitch.conf
but that is not present in the rkt container.
Do not only bind-mount /etc but also the target
of the symlink. With a broken nsswitch.conf
any entries in /etc/hosts are not considered
which makes problems when a custom DNS server
is used.
@pothos pothos requested a review from dongsupark January 27, 2020 14:47
@pothos pothos merged commit 96547fb into flatcar-master-edge Jan 27, 2020
@pothos pothos deleted the kai/oem-gce-rkt-dns-edge branch January 27, 2020 15:40
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants