Arch Linux

pacan_alex

Member

Registered: 2019-02-03

Posts: 1

Docker containers don't start after migration

I've copied Arch Linux installation from HDD to SSD with

rsync -axHAWXS —numeric-ids —info=progress2

and now all docker containers don't start, even the "Hello world" container. How can I fix it?

docker -D (when starting a container with docker start)

ERRO[2019-02-02T20:39:03.196658056+07:00] error unmounting /var/lib/docker/overlay2/68bfac8b3b52a8bc20bd67abf7fe8c4da057c00ab02d20bde881852c502dfd50/merged: invalid argument  storage-driver=overlay2
WARN[2019-02-02T20:39:03.212065592+07:00] error locating sandbox id 3f2f3591ff1136eb006ce8807daf8737b66290fd812cafdb4802664b688f2542: sandbox 3f2f3591ff1136eb006ce8807daf8737b66290fd812cafdb4802664b688f2542 not found 
DEBU[2019-02-02T20:39:03.212223698+07:00] Failed to unmount 68bfac8b3b52a8bc20bd67abf7fe8c4da057c00ab02d20bde881852c502dfd50 overlay: /var/lib/docker/overlay2/68bfac8b3b52a8bc20bd67abf7fe8c4da057c00ab02d20bde881852c502dfd50/merged - no such file or directory  storage-driver=overlay2
ERRO[2019-02-02T20:39:03.212358121+07:00] 33d3b905aff6a68bf3e8cd0a17c6735e32c995582640ce16558e9c4adce6086e cleanup: failed to delete container from containerd: no such container 
DEBU[2019-02-02T20:39:03.212392254+07:00] FIXME: Got an API for which error does not match any expected type!!!: error creating overlay mount to /var/lib/docker/overlay2/68bfac8b3b52a8bc20bd67abf7fe8c4da057c00ab02d20bde881852c502dfd50/merged: stale NFS file handle  error_type="*errors.errorString" module=api
ERRO[2019-02-02T20:39:03.212403667+07:00] Handler for POST /v1.38/containers/eager_shtern/start returned error: error creating overlay mount to /var/lib/docker/overlay2/68bfac8b3b52a8bc20bd67abf7fe8c4da057c00ab02d20bde881852c502dfd50/merged: stale NFS file handle 
DEBU[2019-02-02T20:39:03.212432686+07:00] FIXME: Got an API for which error does not match any expected type!!!: error creating overlay mount to /var/lib/docker/overlay2/68bfac8b3b52a8bc20bd67abf7fe8c4da057c00ab02d20bde881852c502dfd50/merged: stale NFS file handle  error_type="*errors.errorString" module=api

docker info:

Containers: 6
 Running: 0
 Paused: 0
 Stopped: 6
Images: 4
Server Version: 18.06.1-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: 69663f0bd4b60df09991c08812a60108003fa340
init version: fec3683
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.18.12-arch1-1-ARCH
Operating System: Arch Linux
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 15.63GiB
ID: 4374:S5PP:SZN3:4G5N:LCRL:2ITA:XHOL:A3RQ:YEHI:4HN4:HPK7:KOSF
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 22
 Goroutines: 42
 System Time: 2019-02-02T20:47:46.615561579+07:00
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

firecat53

Member

From: Lake Stevens, WA, USA

Registered: 2007-05-14

Posts: 1,542

Website

Re: Docker containers don't start after migration

I don't think it's likely that images based on an overlay filesystem will work correctly when copied, even with rsync. You really need to rebuild/re-pull your images for a migration between disks. You probably should nuke /var/lib/docker and start over.

---

Github