summaryrefslogtreecommitdiff
path: root/vendor/google.golang.org/grpc/status/status.go
diff options
context:
space:
mode:
authorValentin Rothberg <rothberg@redhat.com>2021-12-15 14:41:47 +0100
committerValentin Rothberg <rothberg@redhat.com>2021-12-16 15:31:29 +0100
commitf241efb17993a3234008ed95e899ad1ae849fca0 (patch)
tree4ddca05b1e82e2edb548418a7000794a7574fc0c /vendor/google.golang.org/grpc/status/status.go
parentd984fec351c06a95f8a51c7e6ced819c6b17245f (diff)
downloadpodman-f241efb17993a3234008ed95e899ad1ae849fca0.tar.gz
podman-f241efb17993a3234008ed95e899ad1ae849fca0.tar.bz2
podman-f241efb17993a3234008ed95e899ad1ae849fca0.zip
bindings rmi test: clarify behavior
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: #12441 Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
Diffstat (limited to 'vendor/google.golang.org/grpc/status/status.go')
0 files changed, 0 insertions, 0 deletions