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

network create: do not allow default as name #17175

Merged

Conversation

Luap99
Copy link
Member

@Luap99 Luap99 commented Jan 20, 2023

default is already used as network mode, i.e. podman run --network default will choose the default mode not a network named default.

We already block names from other network modes, default was forgotten.

Fixes #17169

Signed-off-by: Paul Holzinger pholzing@redhat.com

Does this PR introduce a user-facing change?

`podman network create` no longer accepts `default` as valid name, it is impossible to use this network name in the `podman run/create` command because it was parsed as network mode instead.

`default` is already used as network mode, i.e. podman run --network
default will choose the default mode not a network named `default`.

We already block names from other network modes, default was forgotten.

Fixes containers#17169

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 20, 2023

[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 Jan 20, 2023
@mheon
Copy link
Member

mheon commented Jan 20, 2023

LGTM

@baude
Copy link
Member

baude commented Jan 20, 2023

/hold
/lgtm

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 20, 2023
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 20, 2023
@TomSweeneyRedHat
Copy link
Member

LGTM
but a couple of test looked to have flaked, I restarted them.

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
restarted a last flaked job

@Luap99
Copy link
Member Author

Luap99 commented Jan 20, 2023

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 20, 2023
@openshift-merge-robot openshift-merge-robot merged commit 4f4dce1 into containers:main Jan 20, 2023
@Luap99 Luap99 deleted the default-invalid-netname branch January 20, 2023 16:19
@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 14, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 14, 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. release-note
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: DNS doesn't work for containers
6 participants