-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Allow '/' to prefix container names to match Docker #16820
Conversation
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.
I think there's more to unpack since Docker strips off the leading '/'. '/foo' create the name "foo" and it will also be stripped of in regexes. Yet ^/foo$
is not a valid regex to me.
docker always stores the name with a leading podman/pkg/api/handlers/compat/containers.go Line 497 in 1b677c5
So if you apply a filter via docker api we must also add the slash to the name before running the filter regex. |
58572cd
to
cb9eb71
Compare
cmd/podman/utils/utils.go
Outdated
@@ -139,3 +140,11 @@ func IsCheckpointImage(ctx context.Context, namesOrIDs []string) (bool, error) { | |||
} | |||
return true, nil | |||
} | |||
|
|||
func RemoveSlash(input []string) []string { | |||
var output []string |
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.
Can initialize this with make([]string, 0, len(input))
to ensure we only do one allocation
@vrothberg @Luap99 @mheon PTAL |
Code LGTM |
Fixes: containers#16663 Signed-off-by: Daniel J Walsh <[email protected]>
@containers/podman-maintainers PTAL |
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, rhatdan 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 |
/cherry-pick v4.4 |
@baude: #16820 failed to apply on top of branch "v4.4":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This is already in the v4.4 branch |
Fixes: #16663
Signed-off-by: Daniel J Walsh [email protected]
Does this PR introduce a user-facing change?