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 rootless cni dns without systemd stub resolver #11230

Merged
merged 1 commit into from
Aug 16, 2021

Conversation

Luap99
Copy link
Member

@Luap99 Luap99 commented Aug 16, 2021

When a host uses systemd-resolved but not the resolved stub resolver the
following symlinks are created: /etc/resolv.conf ->
/run/systemd/resolve/stub-resolv.conf -> /run/systemd/resolve/resolv.conf.
Because the code uses filepath.EvalSymlinks we put the new resolv.conf
to /run/systemd/resolve/resolv.conf but the /run/systemd/resolve/stub-resolv.conf
link does not exists in the mount ns.
To fix this we will walk the symlinks manually until we reach the first
one under /run and use this for the resolv.conf file destination.

This fixes a regression which was introduced in e73d482.

Fixes #11222

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 16, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 16, 2021
When a host uses systemd-resolved but not the resolved stub resolver the
following symlinks are created: `/etc/resolv.conf` ->
`/run/systemd/resolve/stub-resolv.conf` -> `/run/systemd/resolve/resolv.conf`.
Because the code uses filepath.EvalSymlinks we put the new resolv.conf
to `/run/systemd/resolve/resolv.conf` but the `/run/systemd/resolve/stub-resolv.conf`
link does not exists in the mount ns.
To fix this we will walk the symlinks manually until we reach the first
one under `/run` and use this for the resolv.conf file destination.

This fixes a regression which was introduced in e73d482.

Fixes containers#11222

Signed-off-by: Paul Holzinger <[email protected]>
Copy link
Member

@vrothberg vrothberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rhatdan
Copy link
Member

rhatdan commented Aug 16, 2021

Yikes nasty.
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 16, 2021
@openshift-ci openshift-ci bot merged commit 9ee9d4a into containers:main Aug 16, 2021
@Luap99 Luap99 deleted the rootless-dns branch August 16, 2021 12:47
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 22, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

rootless: no DNS for containers within created network + host not using resolved stub resolver
3 participants