-
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
[podman-remote] command ps
with option --ns
does not work well
#2938
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
openshift-ci-robot
added
the
kind/bug
Categorizes issue or PR as related to a bug.
label
Apr 15, 2019
Using master I cannot replicate your findings. Here is my example:
Do you suspect the container you created matters? |
It's been more than 20 days, I don't have the old created containers now. So I tried it with a new simple container on podman node:
The same result I got on the remote node:
But on podman node, it just works fine:
On podman node:
on remote node:
|
baude
added a commit
to baude/podman
that referenced
this issue
May 7, 2019
the namespace for the remote client was being incorrectly derived from the "remote" client. fixes: containers#2938 Signed-off-by: baude <[email protected]>
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 24, 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.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
On the remote node,
ps
command with option--ns
does not show the namespace information.Steps to reproduce the issue:
PODMAN_VARLINK_ADDRESS="tcp:127.0.0.1:1234" bin/podman-remote ps --ns
Describe the results you received:
Describe the results you expected:
Should have the same result as the podman node does:
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:The text was updated successfully, but these errors were encountered: