How to move docker containers using mapper to another computer without using docker commands

Here is the situation

After the reboot, the docker could not restart due to lack of disk space. Due to many bad decisions, we are now left with only a copy of /var/lib/docker (therefore, we cannot start docker , which we would like to move to another machine with the same OS / version of docker ( 1.8.3 )

when we try to naively replace /var/lib/docker with the old one, we get

 Feb 20 08:06:33 example.com systemd[1]: Starting Docker Application Container Engine... Feb 20 08:06:33 example.com docker[2164]: time="2016-02-20T08:06:33.111285635+01:00" level=error msg="[graphdriver] prior storage driver \"devicemapper\" failed: Base Device UUID verification failed. Possibly using a different thin pool then last invocation:exit status 2" Feb 20 08:06:33 example.com docker[2164]: time="2016-02-20T08:06:33.111382676+01:00" level=fatal msg="Error starting daemon: error initializing graphdriver: Base Device UUID verification failed. Possibly using a different thin pool then last invocation:exit status 2" Feb 20 08:06:33 example.com systemd[1]: docker.service: main process exited, code=exited, status=1/FAILURE 

I read this problem on docker https://github.com/docker/docker/issues/15721 , but this does not seem to be useful.

Is there a known procedure for moving things? or at least to install disk images to receive data?

+6
source share
2 answers

workaround - rm -rf / var / lib / docker and reload dockers (sometimes a host reboot is required)

https://github.com/docker/docker/issues/23089

+1
source

You can change the UUID for which docker is looking in / var / lib / docker / devicemapper / metadata / deviceset -metadata p>

this file is contained in my system:

 { "BaseDeviceFilesystem": "xfs", "BaseDeviceUUID": "4c799443-bf3d-4b95-a9df-dd86de235057", "next_device_id": 1 } 

You should try replacing 4c799443-bf3d-4b95-a9df-dd86de235057 with the UUID Dock.

+1
source

All Articles