-
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
bindings rmi test: clarify behavior #12606
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vrothberg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Changes look OK to me, but the tests aren't at all happy. |
search on registry.access.redhat.com/* is broken. All tests in all PRs are red at the moment :^) |
LGTM |
rebased to fix the search flake ✔️ |
/lgtm |
Unintended consequences
|
The libpod/images/remove endpoint is not very REST-ish but, after some debate, was decided to be implemented as for the following reasons. First, it allows for batch removing images which improves performance significantly. Note that Docker does support `rmi -a`! Second, it allows for hiding the logic of setting the right exit code to use from the client and keep all the logic on the server. Hence, when removing an image that does not exist, the server will return a 200. The response, however, includes the error message to be used *and* the exit code that podman-remote will use. Fixes: containers#12441 Signed-off-by: Valentin Rothberg <[email protected]>
ready to merge |
/lgtm |
The libpod/images/remove endpoint is not very REST-ish but, after some
debate, was decided for it to be implemented as is for the following reasons.
First, it allows for batch removing images which improves performance
significantly. Note that Docker does support
rmi -a
!Second, it allows for hiding the logic of setting the right exit code to
use from the client and keep all the logic on the server.
Hence, when removing an image that does not exist, the server will
return a 200. The response, however, includes the error message to be
used and the exit code that podman-remote will use.
Fixes: #12441
Signed-off-by: Valentin Rothberg [email protected]
@edsantiago PTAL