8.2.1.4 Named Volume Reuse

Named volume reuse is the practice of intentionally reattaching the same named volume across multiple, separate container runs — whether recreating a service after an update or sharing data between distinct containers — relying on the volume's stable, explicit name to consistently reference the exact same underlying data.

Reusing a Volume Across Container Recreations

Recreating a container while referencing the same named volume reliably picks up exactly where the previous container left off.

docker run -d --name app -v app-data:/data myapp:1.0
docker stop app && docker rm app
docker run -d --name app -v app-data:/data myapp:2.0

The new container, running an updated image version, has the exact same data available as the previous container did, since both explicitly reference app-data.

Reusing a Volume Across Entirely Different Containers

A named volume can also be intentionally shared between two different containers serving different purposes, when both genuinely need access to the same underlying data.

docker run -d --name web-server -v shared-uploads:/var/www/uploads nginx:alpine
docker run -d --name upload-processor -v shared-uploads:/data/incoming processor:1.0

Both containers access the identical underlying data through the shared, named volume, despite serving entirely different roles.

Why Explicit Naming Is What Makes Reuse Reliable

Because the volume's name is explicit and consistent, there's no ambiguity about which specific volume is being referenced — this reliability is precisely what anonymous volumes, with their randomly generated names, cannot provide as conveniently.

docker volume ls --filter name=app-data

Why Named Volume Reuse Matters

Reliable volume reuse — across container updates, recreations, or intentional sharing between related containers — is a core practical benefit of using named volumes consistently, enabling common operational patterns like rolling updates and shared data access between cooperating containers.