標籤:導致 bsp evel app end pid ice [1] info
在一台新機子上面,docker處理完lvs資料卷之後,啟動docker服務時,出現了啟動失敗,失敗資訊如下:
[[email protected] ~]# systemctl status docker● docker.service - Docker Application Container Engine Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/docker.service.d └─flannel.conf Active: failed (Result: exit-code) since Tue 2018-07-24 14:06:15 CST; 4s ago Docs: https://docs.docker.com Process: 28723 ExecStart=/usr/bin/dockerd $DOCKER_NETWORK_OPTIONS $DOCKER_NETWORK_OPTIONS $DOCKER_STORAGE_OPTIONS (code=exited, status=1/FAILURE) Main PID: 28723 (code=exited, status=1/FAILURE) Memory: 412.0K CGroup: /system.slice/docker.serviceJul 24 14:06:14 hxin221 systemd[1]: Starting Docker Application Container Engine...Jul 24 14:06:14 hxin221 dockerd[28723]: time="2018-07-24T14:06:14.416711161+08:00" level=info msg="libcontainerd: new containerd process, pid: 28738"Jul 24 14:06:15 hxin221 dockerd[28723]: Error starting daemon: error initializing graphdriver: devmapper: Base Device UUID and Filesystem verification failed: devicemapper: Error running deviceCreate (ActivateDevice) dm_task_run failedJul 24 14:06:15 hxin221 systemd[1]: docker.service: main process exited, code=exited, status=1/FAILUREJul 24 14:06:15 hxin221 systemd[1]: Failed to start Docker Application Container Engine.Jul 24 14:06:15 hxin221 systemd[1]: Unit docker.service entered failed state.Jul 24 14:06:15 hxin221 systemd[1]: docker.service failed.
總的來說就是:
Error starting daemon: error initializing graphdriver: devmapper: Base Device UUID and Filesystem verification failed: devicemapper: Error running deviceCreate (ActivateDevice) dm_task_run failed
好吧,這個錯誤,之前沒有遇到過,踩了很多坑,最終,想了想,莫非這台機子早先時候已經裝了docker,然後舊資料導致的?
於是乎,就抱著試試看的目的,執行了如下操作:
[[email protected] ~]# rm -rf /var/lib/docker/*
沒錯,清除了docker的資料,由於是新機子,我也沒有做什麼備份處理,其他小夥伴如果又遇到的話,記得先備份資料。
於是,重啟服務
[[email protected] ~]# systemctl restart docker
OK,問題不大,解決了。
以上
devicemapper: Error running deviceCreate (ActivateDevice) dm_task_run failed