Daniel J Walsh 75419c5d88 When removing objects specifying --force,podman should exit with 0 ... This Patch will cause podman COMMAND rm --force bogus not fail This is how Docker works, so Podman should follow this to allow existing scripts to convert from Docker to Podman. Fixes: #14612 Oprignal version of this patch came from wufan 1991849113@qq.com Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>		2022-07-26 16:00:42 -04:00
..
create.go	cmd/podman: switch to golang native error wrapping	2022-06-30 12:58:57 +02:00
exists.go	Add podman volume mount support	2022-02-28 14:26:22 -05:00
export.go	cmd/podman: switch to golang native error wrapping	2022-06-30 12:58:57 +02:00
import.go	cmd/podman: switch to golang native error wrapping	2022-06-30 12:58:57 +02:00
inspect.go	cmd/podman: switch to golang native error wrapping	2022-06-30 12:58:57 +02:00
list.go	cmd/podman: switch to golang native error wrapping	2022-06-30 12:58:57 +02:00
mount.go	Add podman volume mount support	2022-02-28 14:26:22 -05:00
prune.go	bump go module to version 4	2022-01-18 12:47:07 +01:00
reload.go	add podman volume reload to sync volume plugins	2022-06-23 18:36:30 +02:00
rm.go	When removing objects specifying --force,podman should exit with 0	2022-07-26 16:00:42 -04:00
unmount.go	enable staticcheck linter	2022-04-22 12:51:29 +02:00
volume.go	bump go module to version 4	2022-01-18 12:47:07 +01:00