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

cod*_*red 5 docker

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"
Run Code Online (Sandbox Code Playgroud)

我了解此问题的解决方法是删除 /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
Run Code Online (Sandbox Code Playgroud)

谢谢

此致

小智 2

您好,我遇到了同样的问题,解决方案是使用 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"}
Run Code Online (Sandbox Code Playgroud)

就改变它吧!

然后再次启动引擎...您的图像和容器现在可能已经回到您身边了!