mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-10-12 08:57:42 +00:00
7b3d47c3b9
When I reworked pod removal to provide more detailed errors (including per-container errors, not just a single multierror with all errors squashed), I made it part of the struct returned by the REST API and assumed that would be enough to get errors through to clients. Unfortunately, in case of an overarching error removing the pod (as any error with any container would cause), we don't send the response struct that would include the container errors - we just send a standardized REST error. We could work around this with custom, potentially backwards incompatible error handling for the REST pod delete endpoint, or we could just do what was done before, and package up all the errors in a multierror to send to the other side. Of those options, the multierror seems far simpler. Fixes #19159 Signed-off-by: Matt Heon <mheon@redhat.com> |
||
|---|---|---|
| .. | ||
| containers.go | ||
| containers_create.go | ||
| containers_stats.go | ||
| generate.go | ||
| healthcheck.go | ||
| images.go | ||
| images_pull.go | ||
| images_push.go | ||
| info.go | ||
| kube.go | ||
| manifests.go | ||
| networks.go | ||
| play.go | ||
| pods.go | ||
| secrets.go | ||
| swagger_spec.go | ||
| system.go | ||
| volumes.go | ||