Open josh-shaw-dev opened 8 years ago
Can you check if you get same error on regular upgrade?
I have upgraded to 1.9.1 to get away from the network interface error in the mean time, I cant have it down for the estimated 6 hours or so as its a prod instance.
Ill see if I get some time to clone it and run it locally for more in-depth testing.
i get the same error in Docker 1.6.2 env
docker run --privileged --rm -v /var/lib/docker:/var/lib/docker docker/v1.10-migrator
time="2016-03-22T08:02:53Z" level=debug msg="layer eff9922ad47c3fa9d350b7959f08f28172624eadec8e62ba1febf8e55ee259d9 took 0.01 seconds" time="2016-03-22T08:02:53Z" level=debug msg="devmapper: activateDeviceIfNeeded(d84fd19c22ca9e54b41d332b01ee3d7067624f2a9271acc707f779d2bdf0ade7)" time="2016-03-22T08:02:53Z" level=error msg="could not calculate checksum for \"d84fd19c22ca9e54b41d332b01ee3d7067624f2a9271acc707f779d2bdf0ade7\", \"Can't create snap device: devmapper: Error activating devmapper device for 'd84fd19c22ca9e54b41d332b01ee3d7067624f2a9271acc707f779d2bdf0ade7': devicemapper: Error running deviceCreate (ActivateDevice) dm_task_run failed\""
Output of docker version:
Client version: 1.6.2 Client API version: 1.18 Go version (client): go1.4.2 Git commit (client): ba1f6c3/1.6.2 OS/Arch (client): linux/amd64 Server version: 1.6.2 Server API version: 1.18 Go version (server): go1.4.2 Git commit (server): ba1f6c3/1.6.2 OS/Arch (server): linux/amd64
Docker Info
Containers: 0 Images: 33 Storage Driver: devicemapper Pool Name: docker-202:2-1705646-pool Pool Blocksize: 65.54 kB Backing Filesystem: extfs Data file: /dev/loop0 Metadata file: /dev/loop1 Data Space Used: 1.412 GB Data Space Total: 107.4 GB Data Space Available: 50.84 GB Metadata Space Used: 2.204 MB Metadata Space Total: 2.147 GB Metadata Space Available: 2.145 GB Udev Sync Supported: true Data loop file: /var/lib/docker/devicemapper/devicemapper/data Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata Library Version: 1.02.107-RHEL7 (2015-12-01) Execution Driver: native-0.2 Kernel Version: 3.10.0-327.10.1.el7.x86_64 Operating System: CentOS Linux 7 (Core) CPUs: 2 Total Memory: 3.451 GiB Name: zdocker-test ID: P36S:DFNJ:VGWR:4P72:5PZS:2NII:FI6D:YSA6:YRFF:BV74:TPYX:P6MD
So I am having issues running the migratory tool, the tool which finishes in about a minute or so, expected to be run four about 6 hours or so with the amount of data.
Trying to upgrade so I can get away from these errors. Referenced here https://github.com/docker/docker/issues/14738 time="2016-03-16T22:40:07.797402232Z" level=error msg="Handler for POST /containers/{name:.*}/start returned error: Cannot start container 6d2de143cde8bb3b510c95c44ac115d256909876497d32113ecc6a5d02f73731: adding interface veth2e4eadf to bridge docker0 failed: could not find bridge docker0: no such network interface"
Some more info of use, the /var/lib/docker is linked to a mounted in volume in /var/data on the host
Command run: sudo docker run -d --privileged -v /var/lib/docker:/var/lib/docker docker/v1.10-migrator -s devicemapper
docker info
docker version: