A bug was identified in the Docker platform that can cause loss of data on volumes when they are removed. The bug is triggered if a volume cannot be unmounted once it’s no longer used by any Docker containers, leaving the volume in an incorrect state. If such a volume is removed with
docker volume rm, the data in the backing store is lost.
The bug will typically be triggered if using local volumes with mount options or using NFS-backed volumes. Volumes that use external drivers (volume plugins) are not affected.
The bug can also be triggered if using Docker Trusted Registry (DTR) with NFS storage — if you installed DTR with the
--nfs-storage-url option or if you manually mounted an NFS share in DTR.
When DTR is using NFS
destroy , operations can result in DTR data loss.
An update that fixes the bug will be made available for all Docker versions starting from 1.11 and later, and the bug will also be fixed in the upcoming Docker 17.06 release.
The bug affects all versions of Docker with volume support, including 1.11, 1.12, 1.13, 17.03 and earlier releases. Updates will be made available to all Docker versions starting from 1.11.
Docker Universal Control Plane and Docker Trusted Registry do not require separate updates, and you can continue to use your currently deployed version of UCP and DTR. Only the Docker EE platform (previously Docker CS Engine) itself requires updates to fix the bug.
If you are not using local or NFS volumes with Docker, no update is required. Docker encourages customers stay current and up-to-date with new Docker releases.
Docker will make updates available to Docker 17.03, 1.13, 1.12 and 1.11.
Until updates from Docker are ready, the following temporary workarounds are available:
- Before running
docker volume rm, check the mount table with
mount -land manually unmount volumes with
- If using DTR with NFS, avoid
destroyoperations until an update is available.
- For DTR, pre-create the volume as a Docker NFS volume instead of manually mounting an NFS share over the volume directory.
Please contact our Support if you have any questions or concerns.