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

podman --help: spurious "Usage of remote" in stderr #7273

Closed
edsantiago opened this issue Aug 10, 2020 · 0 comments · Fixed by #7358
Closed

podman --help: spurious "Usage of remote" in stderr #7273

edsantiago opened this issue Aug 10, 2020 · 0 comments · Fixed by #7358
Assignees
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.

Comments

@edsantiago
Copy link
Member

$ podman --help
Usage of remote:
  -r, --remote
Manage pods, containers and images
....

The "Usage of remote" is jarring and unnecessary. It also goes to stderr, not stdout. git bisect blames 98da2fa. @jwhonce PTAL

@jwhonce jwhonce self-assigned this Aug 10, 2020
@jwhonce jwhonce added the kind/bug Categorizes issue or PR as related to a bug. label Aug 10, 2020
jwhonce added a commit to jwhonce/podman that referenced this issue Aug 18, 2020
--remote pre-check was providing usage context, which was also being
provided by the root podman command.

Fixes containers#7273

Signed-off-by: Jhon Honce <[email protected]>
edsantiago added a commit to edsantiago/libpod that referenced this issue Aug 19, 2020
info, images, run, networking tests: remove some skip_if_remote()s
that were added in the varlink days. All of these tests now seem
to work with APIv2.

help test: check that first output line from 'podman --help'
is the program description (regression check for containers#7273).

load test: clean up stray images, rewrite test to make it conform
to existing convention. In the process, discover and file containers#7337

exec test (and networking): file containers#7360, and add FIXME comment
to skip()s suggesting evaluating those tests once that is fixed.

pod test: now that containers#6328 is fixed, use 'podman pod inspect --format'
instead of relying on jq

Various other tests: add an explanation of why test is disabled
so we can more easily distinguish "this will never be meaningful
under remote" vs "hey, doesn't work for now, but maybe someday".

Signed-off-by: Ed Santiago <[email protected]>
Luap99 pushed a commit to Luap99/libpod that referenced this issue Aug 30, 2020
--remote pre-check was providing usage context, which was also being
provided by the root podman command.

Fixes containers#7273

Signed-off-by: Jhon Honce <[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 22, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants