Docker daemon could not start: does not match with stored UUID error fix

Docker daemon failed to start: does not match with stored UUID error

When I was working on a project recently, I encountered the problem that Docker daemon could not start: does not match with stored UUID was wrong. I solved the problem by searching online materials, and here is the solution.

Docker USES the loop device to store images by default. Use /var/lib/docker for storage. But when the root partition is not large enough (the default installation of Centos7 is only 50G), that's a problem.

The following modification methods are provided (take the centos7 operating system as an example) :

1. systemctl stop docker

2. mount /dev/sdb1 /tmp

3. cp -arf /var/lib/docker/* /tmp

4. rm -rf /var/lib/docker

5. umount /tmp; mount /dev/sdb1 /var/lib/docker

6. systemctl start docker

If an error is reported while performing step 6:

Nov 03 15:35:47 master-57 dockerd[11586]: time="2016-11-03T15:35:47.950627346+08:00" level=error msg="[graphdriver] prior storage driver \"devicemapper\" failed: devmapper: Base Device UUID and Filesystem verification failed: devmapper:Current Base Device UUID:15b94e74-7712-44bc-b695-9c2c633b8b3a does not match with stored UUID:cba4570c-421a-4612-8030-e7734d6365c7. Possibly using a different thin pool than last invocation"
Nov 03 15:35:47 master-57 dockerd[11586]: time="2016-11-03T15:35:47.950782770+08:00" level=fatal msg="Error starting daemon: error initializing graphdriver: devmapper: Base Device UUID and Filesystem verification failed: devmapper: Current Base Device UUID:15b94e74-7712-44bc-b695-9c2c633b8b3a does not match with stored UUID:cba4570c-421a-4612-8030-e7734d6365c7. Possibly using a different thin pool than last invocation"

Then modify it as follows:

stored UUID stored in/var lib docker/devicemapper/metadata/deviceset - metadata inside. Instead, Current Base Device UUID.

Thank you for reading, I hope to help you, thank you for your support of this site!