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 start with filter only starts first result #18153
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
windows
issue/bug on Windows
Comments
github-actions
bot
added
remote
Problem is in podman-remote
windows
issue/bug on Windows
labels
Apr 12, 2023
Thanks for reaching out, @gricey432! I can reproduce on Linux as well with the remote client. |
vrothberg
added a commit
to vrothberg/libpod
that referenced
this issue
Apr 14, 2023
Fix a number of bugs wrt. filtering remote containers and how to process specified names or IDs. I _really_ do not like the duplication between remote and local Podman but want to focus on fixing containers#18153 for now. What I desire in the future is to consolidate all functionality of looking up containers (all, latest, filters, specified names/IDs, etc.) and for remote clients to just call containers/list etc. Fixes: containers#18153 Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
vrothberg
added a commit
to vrothberg/libpod
that referenced
this issue
Apr 14, 2023
Fix a number of bugs wrt. filtering remote containers and how to process specified names or IDs. I _really_ do not like the duplication between remote and local Podman but want to focus on fixing containers#18153 for now. What I desire in the future is to consolidate all functionality of looking up containers (all, latest, filters, specified names/IDs, etc.) and for remote clients to just call containers/list etc. Fixes: containers#18153 Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
vrothberg
added a commit
to vrothberg/libpod
that referenced
this issue
Apr 17, 2023
Fix a number of bugs wrt. filtering remote containers and how to process specified names or IDs. I _really_ do not like the duplication between remote and local Podman but want to focus on fixing containers#18153 for now. What I desire in the future is to consolidate all functionality of looking up containers (all, latest, filters, specified names/IDs, etc.) and for remote clients to just call containers/list etc. Fixes: containers#18153 Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
vrothberg
added a commit
to vrothberg/libpod
that referenced
this issue
Apr 17, 2023
Fix a number of bugs wrt. filtering remote containers and how to process specified names or IDs. I _really_ do not like the duplication between remote and local Podman but want to focus on fixing containers#18153 for now. What I desire in the future is to consolidate all functionality of looking up containers (all, latest, filters, specified names/IDs, etc.) and for remote clients to just call containers/list etc. Fixes: containers#18153 Signed-off-by: Valentin Rothberg <vrothberg@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
Aug 26, 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.
remote
Problem is in podman-remote
windows
issue/bug on Windows
Issue Description
Running the following command on windows only starts the first container in the list.
This command is taken from https://github.com/containers/podman/blob/main/contrib/systemd/system/podman-restart.service.in
I'm unsure if this is windows specific, but I feel like if the service was broken on Linux someone would have reported that by now and I can't find anything.
Steps to reproduce the issue
Steps to reproduce the issue
podman ps --filter "restart-policy=always" --all
podman start --filter "restart-policy=always" --all
Describe the results you received
On the first execution of the command, the first container is started and its ID returned. Running the command again is a noop
Describe the results you expected
The first run of the command should start all filtered containers
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Set up through podman-desktop
Additional information
No response
The text was updated successfully, but these errors were encountered: