aboutsummaryrefslogtreecommitdiff
path: root/pkg/domain/entities/containers.go
diff options
context:
space:
mode:
authorDaniel J Walsh <dwalsh@redhat.com>2020-10-07 14:47:52 -0400
committerDaniel J Walsh <dwalsh@redhat.com>2020-10-09 06:06:08 -0400
commitfea78d5530f996d008912584761433023491f160 (patch)
tree61fc3f7a53b77d53d7d9e1100b3d1ae8497a3794 /pkg/domain/entities/containers.go
parent9ae873e60e149677db66782eaf2b4ed1402e97d2 (diff)
downloadpodman-fea78d5530f996d008912584761433023491f160.tar.gz
podman-fea78d5530f996d008912584761433023491f160.tar.bz2
podman-fea78d5530f996d008912584761433023491f160.zip
This PR allows users to remove external containers directly
Currenly if a user specifies the name or ID of an external storage container, we report an error to them. buildah from scratch working-container-2 podman rm working-container-2 Error: no container with name or ID working-container-2 found: no such container Since the user specified the correct name and the container is in storage we force them to specify --storage to remove it. This is a bad experience for the user. This change will just remove the container from storage. If the container is known by libpod, it will remove the container from libpod as well. The podman rm --storage option has been deprecated, and removed from docs. Also cleaned documented options that are not available to podman-remote. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Diffstat (limited to 'pkg/domain/entities/containers.go')
-rw-r--r--pkg/domain/entities/containers.go1
1 files changed, 0 insertions, 1 deletions
diff --git a/pkg/domain/entities/containers.go b/pkg/domain/entities/containers.go
index 7b272f01e..3b6dd106f 100644
--- a/pkg/domain/entities/containers.go
+++ b/pkg/domain/entities/containers.go
@@ -131,7 +131,6 @@ type RmOptions struct {
Force bool
Ignore bool
Latest bool
- Storage bool
Volumes bool
}