Networks and Volumes

The network and volume command groups expose every operation the GUI offers for these two resource types. Both follow the same patterns as container and image: list, inspect, create, remove/prune, plus relationship commands for networks.

Networks

List and inspect

dockerman network list
dockerman network list --pretty
dockerman network inspect bridge

Create

dockerman network create my-net \
  --driver bridge \
  --attachable \
  --enable-ipv6 \
  --option "com.docker.network.bridge.name=my-bridge" \
  --label "owner=team-a"

Remove

dockerman network remove my-net --yes

remove requires --yes. Built-in networks (bridge, host, none) cannot be removed.

Connect and disconnect

dockerman network connect my-net web
dockerman network disconnect my-net web --force

--force is forwarded to Docker. Dockerman does not require it solely because a container is running; use it only when Docker's disconnect semantics require it.

Volumes

List and inspect

dockerman volume list
dockerman volume list --pretty
dockerman volume inspect data

Create

dockerman volume create data \
  --driver local \
  --driver-opt "type=nfs" \
  --driver-opt "o=addr=10.0.0.1,rw" \
  --driver-opt "device=:/exports/data" \
  --label "backup=daily"

--driver-opt and --label are both repeatable.

Remove

dockerman volume remove data --force --yes

remove requires --yes. --force is forwarded to Docker and does not guarantee removal of a volume that Docker still considers in use.

Prune

dockerman volume prune --filter "label=temp=true" --yes

prune deletes every dangling (unreferenced) volume that matches the filter set. --filter is repeatable and uses Docker's standard filter syntax (label=, label!=, etc.). Always combine with explicit filters in scripts — bare volume prune --yes deletes every dangling volume on the host.