Docker 当前基本设备UUID:与存储的UUID不匹配：

Docker出现故障，因此我重新启动了服务，该服务未启动，我收到以下错误：

error msg="[graphdriver] prior storage driver \"devicemapper\" failed: devmapper: Base Device UUID and Filesystem verification failed: devmapper: Current Base Device UUID: does not match with stored UUID:696f3567-83d7-48d7-9675-688e8543534b. Possibly using a different thin pool than last invocation"

我知道这个问题的解决方法是删除/var/lib/docker的内容，然后重新启动

在不删除容器数据或图像的情况下，是否有此问题的解决方案或解决方法

在调试模式下启动docker时，我会得到以下结果：

WARN[0002] devmapper: Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man docker` to refer to dm.thinpooldev section.
DEBU[0002] devmapper: activateDeviceIfNeeded()
DEBU[0002] devmapper: UUID for device: /dev/mapper/docker-253:1-134790422-base is:
DEBU[0002] devmapper: deactivateDevice()
DEBU[0002] devmapper: removeDevice START(docker-253:1-134790422-base)
DEBU[0002] devmapper: removeDevice END(docker-253:1-134790422-base)
DEBU[0002] devmapper: deactivateDevice END()
DEBU[0002] devmapper: Error device setupBaseImage: devmapper: Base Device UUID and Filesystem verification failed: devmapper: Current Base Device UUID: does not match with stored UUID:696f3567-83d7-48d7-9675-688e8543534b. Possibly using a different thin pool than last invocation
ERRO[0002] [graphdriver] prior storage driver "devicemapper" failed: devmapper: Base Device UUID and Filesystem verification failed: devmapper: Current Base Device UUID: does not match with stored UUID:696f3567-83d7-48d7-9675-688e8543534b. Possibly using a different thin pool than last invocation
DEBU[0002] Cleaning up old mountid : start.
FATA[0002] Error starting daemon: error initializing graphdriver: devmapper: Base Device UUID and Filesystem verification failed: devmapper: Current Base Device UUID: does not match with stored UUID:696f3567-83d7-48d7-9675-688e8543534b. Possibly using a different thin pool than last invocat

多谢各位

---

致以最诚挚的问候

您好，我遇到了同样的问题，解决方案是使用blkid在/dev/loop0上查看实际的UUID

示例/dev/loop0:UUID=“12345678-e192-482e-81c6-9f703db548b6”TYPE=“xfs”

基本设备在文件（/var/lib/docker/deviceapper/metadata/deviceset-metadata）中配置：

只要改变它

---

然后再次启动引擎。。。您的图像和容器现在可能已经返回给您了

您还可以删除

UUID

，即

{"next_device_id":1,"BaseDeviceUUID":"","BaseDeviceFilesystem":"xfs"}

---

Docker将在您下次启动守护程序时完成此操作。

这帮助了我今天在Fedora下使用devicemapper和NTFS时遇到了完全相同的错误，thx！

{"next_device_id":1,"BaseDeviceUUID":"","BaseDeviceFilesystem":"xfs"}