Question

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

谢谢

祝你好运

Answer 1

您好我有同样的问题，解决方法是使用blkid查看/ dev / loop0上的实际UUID

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

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

{"next_device_id":1,"BaseDeviceUUID":"**OLD-UUID**","BaseDeviceFilesystem":"xfs"}

只需改变它！

再次启动引擎......你的图像和容器现在可能已经回复给你了！

Answer 2

您也可以删除UUID，即

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

并且Docker将在您下次启动守护程序时完成它。

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

2 个答案: