-
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 ps -a --filter "status=exited" does not work #5050
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
Feb 2, 2020
/kind bug |
The filter itself is working, but Podman seems to be retaining the default behavior (show only running containers) even when |
mheon
added a commit
to mheon/libpod
that referenced
this issue
Feb 4, 2020
When we filter, it should be out of all containers, not just running ones, by default - this is necessary to ensure Docker compatability. Fixes containers#5050 Signed-off-by: Matthew Heon <mheon@redhat.com>
mheon
added a commit
to mheon/libpod
that referenced
this issue
Feb 4, 2020
When we filter, it should be out of all containers, not just running ones, by default - this is necessary to ensure Docker compatability. Fixes containers#5050 Signed-off-by: Matthew Heon <mheon@redhat.com>
sujil02
pushed a commit
to sujil02/podman
that referenced
this issue
Feb 7, 2020
When we filter, it should be out of all containers, not just running ones, by default - this is necessary to ensure Docker compatability. Fixes containers#5050 Signed-off-by: Matthew Heon <mheon@redhat.com>
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
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
I am unable to filter for Stopped or exited container. I can filter for "status=running" but i am unable to use "status=exited". The bash Script is used on the host container to start/stop root-less container on system startup or shutdown.
So shutdown is not an issue, i perform:
podman ps --filter "status=running" --format "{{.ID}} {{.Image}}" | while read CONT_ID CONT_IMG do echo "shutdown podmans ${CONT_ID} ${CONT_IMG} " podman stop ${CONT_ID} done
But on system-startup i have to do use a workaround like this:
podman ps -a --format "{{.ID}} {{.Image}} {{.Status}} " | grep kivi | grep Exited | while read CONT_ID CONT_IMG CONT_STATUS do echo "starting podmans ${CONT_ID} ${CONT_IMG} " podman start ${CONT_ID} done
Steps to reproduce the issue:
Describe the results you received:
I receive no result when filtering for exited container
Describe the results you expected:
I would like to run this:
podman ps --filter "status=exited" --format "{{.ID}} {{.Image}} {{.Status}} " | grep kivi | grep Exited | while read CONT_ID CONT_IMG CONT_STATUS
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Additional environment details (AWS, VirtualBox, physical, etc.):
It's a Fedora Box.
The text was updated successfully, but these errors were encountered: