Docker / Volumes, Filesystems & Recovery
Find the actual named volume after a deployment appears to lose data
A changed project or explicit volume name can attach a new empty volume while the old data still exists elsewhere.
Environment and inputs: Docker Engine · Compose v2 and Buildx where specified; Linux containers unless noted. Verify daemon context, installed feature support and authorized host or Swarm manager access first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
docker volume ls
docker container inspect --format '{{json .Mounts}}' appRead the result
The inventory and active mapping identify candidate volumes. Similar names do not prove equal content or safe interchangeability.
Resolve and verify
Compare deployment history, labels and the intended data owner, then validate the correct volume through an approved recovery procedure. Reattach only with a reviewed application plan.
Before changing production
Do not prune apparently unused volumes or attach an unverified old database copy to a new application version.