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

Don't error if resolv.conf does not exists #8111

Merged

Conversation

Luap99
Copy link
Member

@Luap99 Luap99 commented Oct 22, 2020

If the resolv.conf file is empty we provide default dns servers.
If the file does not exists we error and don't create the
container. We should also provide the default entries in this
case. This is also what docker does.

Fixes #8089

If the resolv.conf file is empty we provide default dns servers.
If the file does not exists we error and don't create the
container. We should also provide the default entries in this
case. This is also what docker does.

Fixes containers#8089

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

mheon commented Oct 22, 2020

Can you add a test? Take the ALPINE image, build a new version with resolv.conf removed, and ensure a container made from it starts successfully?

@mheon
Copy link
Member

mheon commented Oct 22, 2020

/approve

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Luap99, mheon

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-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 22, 2020
@Luap99
Copy link
Member Author

Luap99 commented Oct 22, 2020

@mheon I'm talking about the /etc/resolv.conf file on the host. I don't think I should remove this file in the CI test VMs.

@mheon
Copy link
Member

mheon commented Oct 22, 2020

Ah, yes, we can't really test for that easily!

@TomSweeneyRedHat
Copy link
Member

LGTM
assuming happy tests

@rhatdan
Copy link
Member

rhatdan commented Oct 22, 2020

Thanks @Luap99
/lgtm
/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 22, 2020
@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 22, 2020
@Luap99
Copy link
Member Author

Luap99 commented Oct 22, 2020

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 22, 2020
@openshift-merge-robot openshift-merge-robot merged commit 2adc1b2 into containers:master Oct 22, 2020
@Luap99 Luap99 deleted the fix-missing-resolv.conf branch October 27, 2020 15:21
@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 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 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.

Missing resolv.conf in WSL2
6 participants