Docker Daemon failed to start: does not match with stored UUID error resolution _docker

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

Recently done project, encountered Docker Daemon Unable to start: does not match with stored UUID error problem, after the Internet to find data to solve the problem, here to record the solution.

Docker uses the loop device to store mirroring by default. Use/var/lib/docker storage. But when the root partition is not big enough (CENTOS7 only 50G installed by default), that's a hassle.

The following modification method is provided here (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 you do an error during step sixth:

Nov 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 Rrent 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 15:35:47 master-57 dockerd[11586
]: time=" 2016-11-03t 15: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 no T match with stored uuid:cba4570c-421a-4612-8030-e7734d6365c7. Possibly using a different thin pool than last invocation "

Then modify the following methods:

The stored UUID is stored inside the/var/lib/docker/devicemapper/metadata/deviceset-metadata. Replace with the current Base Device uuid.

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