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

rootless: add an entry to /etc/hosts when using slirp4netns #3406

Merged

Conversation

giuseppe
Copy link
Member

Closes: #3405

Signed-off-by: Giuseppe Scrivano [email protected]

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: giuseppe

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 Jun 22, 2019
@TomSweeneyRedHat
Copy link
Member

Changes LGTM, just wondering if we should also add a trailing comment to the line too, something like "# used by rootless Podman" or "# used by slirp4netns" or perhaps just "# slirp4netns"

@rhatdan
Copy link
Member

rhatdan commented Jun 23, 2019

@giuseppe Yes please add a comment. Is there a possibility for a conflict here? If the hostname was added twice? What happens?

@giuseppe
Copy link
Member Author

@giuseppe Yes please add a comment. Is there a possibility for a conflict here? If the hostname was added twice? What happens?

comment added. In that case the resolver will use all the specified addresses.

# printf "192.168.10.1 foo\n192.168.10.2 foo\n192.168.10.3 foo\n" >> /etc/hosts
# python -c 'import socket; print(socket.gethostbyname_ex("foo"))'
('foo', [], ['192.168.10.1', '192.168.10.2', '192.168.10.3'])

@rhatdan
Copy link
Member

rhatdan commented Jun 24, 2019

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 24, 2019
@openshift-merge-robot openshift-merge-robot merged commit 33280d8 into containers:master Jun 24, 2019
@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 26, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 26, 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.

hostname not added to /etc/hosts in rootless mode
6 participants