-
Notifications
You must be signed in to change notification settings - Fork 785
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
make use of new pasta option from c/common #5724
make use of new pasta option from c/common #5724
Conversation
Includes my pasta changes Signed-off-by: Paul Holzinger <pholzing@redhat.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: flouthoc, 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 |
We always map 169.254.1.2 with pasta to the host now so ensure the host.containers.internal entry is set correctly. Signed-off-by: Paul Holzinger <pholzing@redhat.com>
0620035
to
5184bf1
Compare
/lgtm |
This was just added as alias to allow vendoring without having to fix all callers at the same time. These are the PRs that updat the callers: containers/podman#24417 containers/buildah#5724 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
This was just added as alias to allow vendoring without having to fix all callers at the same time. These are the PRs that update the callers: containers/podman#24417 containers/buildah#5724 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
What type of PR is this?
/kind feature
What this PR does / why we need it:
Me always map 169.254.1.2 to the host now by default so ensure the
host.containers.internal entry is set correctly.
How to verify it
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?