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.

Sign up for GitHub

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

Jump to bottom

podman-remote: bunch of commands need to reject -l #7127

Closed
edsantiago opened this issue Jul 28, 2020 · 0 comments · Fixed by #7221
Closed

podman-remote: bunch of commands need to reject -l #7127

edsantiago opened this issue Jul 28, 2020 · 0 comments · Fixed by #7221
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. remote Problem is in podman-remote

Comments

@edsantiago
Copy link
Member

-l doesn't work with podman-remote, but a lot of commands accept it anyway:

$ ./bin/podman-remote ps -l
CONTAINER ID  IMAGE   COMMAND  CREATED  STATUS  PORTS   NAMES

$  ./bin/podman-remote diff -l
Error: invalid character 'M' looking for beginning of value

$ ./bin/podman-remote inspect -l
[]

$ ./bin/podman-remote [ wait, start, stop, kill, port, and probably more ]
@edsantiago edsantiago added kind/bug Categorizes issue or PR as related to a bug. remote Problem is in podman-remote labels Jul 28, 2020
@baude baude mentioned this issue Aug 4, 2020
Merged
baude added a commit to baude/podman that referenced this issue Aug 10, 2020
@baude
remove --latest for all remote commands
cd74f66 
instead of hiding the latest options for podman-remote or catching an error if podman --remote <cmd> -l is used, we no longer add the latest option to any remote command.  podman will error with a "unknown flag" option.

Fixes: containers#7127

Signed-off-by: Brent Baude <[email protected]>
mheon pushed a commit to mheon/libpod that referenced this issue Aug 20, 2020
@baude @mheon
remove --latest for all remote commands
14379d6 
instead of hiding the latest options for podman-remote or catching an error if podman --remote <cmd> -l is used, we no longer add the latest option to any remote command.  podman will error with a "unknown flag" option.

Fixes: containers#7127

Signed-off-by: Brent Baude <[email protected]>
@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 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. remote Problem is in podman-remote
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

remove --latest for all remote commands baude/podman
1 participant
@edsantiago