ドッカーので、私はサービスを再起動し、サービスが開始されない誤動作して、私は次のエラーを取得:現在のベースのデバイスのUUID:保存されたUUIDと一致しません:
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の内容を削除してから再起動することです。
コンテナのデータまたはイメージを削除しないと、この問題の解決策または回避策はありますか?
私はデバッグモードでドッキングウィンドウを起動すると、私は、次を得る:
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
は、私は同じ問題を抱えていたこんにちは、解決策は上の実際のUUIDを見ているあなたに
敬具