You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inconsistency for the CLI UX which makes documentation harder and muscle memory more expensive. Adding a simple compatibility option would bring the two UX for volume management closer together.
Steps to reproduce the issue
Steps to reproduce the issue
docker volume prune -a (and podman volume prune -a
Describe the results you received
jon@dahome:~$ docker volume prune -a
Error: unknown shorthand flag: 'a' in -a
See 'podman volume prune --help'
Describe the results you expected
To maintain a compatible UX for the CLI, we should support -a for the volume prune. The default behaviors between docker and podman are different and we should unify them more.
In Docker CE you need to pass -a to do a proper dangling volume cleanup.
In Podman it does the right thing.
We should add -a as compatibility so both docker volume prune -a and podman volume prune -a work.
podman info output
jon@dahome:~$ podman versionClient: Podman EngineVersion: 5.3.0API Version: 5.3.0Go Version: go1.22.7Built: Tue Nov 12 17:00:00 2024OS/Arch: linux/amd64jon@dahome:~$ podman infohost:
arch: amd64buildahVersion: 1.38.0cgroupControllers:
- cpu
- io
- memory
- pidscgroupManager: systemdcgroupVersion: v2conmon:
package: conmon-2.1.12-2.fc40.x86_64path: /usr/bin/conmonversion: 'conmon version 2.1.12, commit: 'cpuUtilization:
idlePercent: 93.91systemPercent: 1.33userPercent: 4.76cpus: 24databaseBackend: sqlitedistribution:
distribution: fedoravariant: workstationversion: "40"eventLogger: journaldfreeLocks: 2047hostname: dahome.damaestro.usidMappings:
gidmap:
- container_id: 0host_id: 1000size: 1
- container_id: 1host_id: 524288size: 65536uidmap:
- container_id: 0host_id: 1000size: 1
- container_id: 1host_id: 524288size: 65536kernel: 6.11.8-200.fc40.x86_64linkmode: dynamiclogDriver: journaldmemFree: 48293961728memTotal: 67290427392networkBackend: netavarknetworkBackendInfo:
backend: netavarkdns:
package: aardvark-dns-1.13.1-1.fc40.x86_64path: /usr/libexec/podman/aardvark-dnsversion: aardvark-dns 1.13.1package: netavark-1.13.0-1.fc40.x86_64path: /usr/libexec/podman/netavarkversion: netavark 1.13.0ociRuntime:
name: crunpackage: crun-1.18.2-1.fc40.x86_64path: /usr/bin/crunversion: |- crun version 1.18.2 commit: 00ab38af875ddd0d1a8226addda52e1de18339b5 rundir: /run/user/1000/crun spec: 1.0.0 +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +LIBKRUN +WASM:wasmedge +YAJLos: linuxpasta:
executable: /usr/bin/pastapackage: passt-0^20241030.gee7d0b6-1.fc40.x86_64version: | pasta 0^20241030.gee7d0b6-1.fc40.x86_64 Copyright Red Hat GNU General Public License, version 2 or later <https://www.gnu.org/licenses/old-licenses/gpl-2.0.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.remoteSocket:
exists: truepath: /run/user/1000/podman/podman.sockrootlessNetworkCmd: pastasecurity:
apparmorEnabled: falsecapabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOTrootless: trueseccompEnabled: trueseccompProfilePath: /usr/share/containers/seccomp.jsonselinuxEnabled: trueserviceIsRemote: falseslirp4netns:
executable: ""package: ""version: ""swapFree: 8589930496swapTotal: 8589930496uptime: 0h 46m 42.00svariant: ""plugins:
authorization: nulllog:
- k8s-file
- none
- passthrough
- journaldnetwork:
- bridge
- macvlan
- ipvlanvolume:
- localregistries:
search:
- registry.fedoraproject.org
- registry.access.redhat.com
- docker.iostore:
configFile: /home/jon/.config/containers/storage.confcontainerStore:
number: 0paused: 0running: 0stopped: 0graphDriverName: overlaygraphOptions: {}graphRoot: /home/jon/.local/share/containers/storagegraphRootAllocated: 998483427328graphRootUsed: 76022562816graphStatus:
Backing Filesystem: btrfsNative Overlay Diff: "true"Supports d_type: "true"Supports shifting: "false"Supports volatile: "true"Using metacopy: "false"imageCopyTmpDir: /var/tmpimageStore:
number: 19runRoot: /run/user/1000/containerstransientStore: falsevolumePath: /home/jon/.local/share/containers/storage/volumesversion:
APIVersion: 5.3.0Built: 1731456000BuiltTime: Tue Nov 12 17:00:00 2024GitCommit: ""GoVersion: go1.22.7Os: linuxOsArch: linux/amd64Version: 5.3.0jon@dahome:~$ rpm -q podmanpodman-5.3.0-1.fc40.x86_64
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
Issue Description
Inconsistency for the CLI UX which makes documentation harder and muscle memory more expensive. Adding a simple compatibility option would bring the two UX for volume management closer together.
Steps to reproduce the issue
Steps to reproduce the issue
docker volume prune -a
(andpodman volume prune -a
Describe the results you received
Describe the results you expected
To maintain a compatible UX for the CLI, we should support
-a
for the volume prune. The default behaviors between docker and podman are different and we should unify them more.In Docker CE you need to pass
-a
to do a proper dangling volume cleanup.In Podman it does the right thing.
We should add
-a
as compatibility so bothdocker volume prune -a
andpodman volume prune -a
work.podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: