moby: docker 19.03-RC3: cp broken with debian containers (arm?)

Description

docker cp is broken with Debian containers (on armhf).

Steps to reproduce the issue:

  1. install the latest docker 19.03 on armhf
  2. docker run --name foo -d debian:buster-slim sleep 1000
  3. docker cp foo:/root/.profile .

Describe the results you received:

Error response from daemon: error processing tar file: docker-tar: relocation error: /lib/arm-linux-gnueabihf/libnss_files.so.2: symbol __libc_readline_unlocked, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference : exit status 127

Describe the results you expected:

Work.

Additional information you deem important (e.g. issue happens only occasionally):

This works fine with:

  • Alpine (musl)
  • BusyBox

This also works fine with Debian on D4M using 19.03-RC2

Output of docker version:

Client: Docker Engine - Community
 Version:           19.03.0-rc3
 API version:       1.40
 Go version:        go1.12.5
 Git commit:        27fcb77
 Built:             Thu Jun 20 02:14:50 2019
 OS/Arch:           linux/arm
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.0-rc3
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.5
  Git commit:       27fcb77
  Built:            Thu Jun 20 02:08:53 2019
  OS/Arch:          linux/arm
  Experimental:     false
 containerd:
  Version:          1.2.6
  GitCommit:        894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc:
  Version:          1.0.0-rc8
  GitCommit:        425e105d5a03fabd737a126ad93d62a9eeede87f
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Output of docker info:

Client:
 Debug Mode: false

Server:
 Containers: 10
  Running: 7
  Paused: 0
  Stopped: 3
 Images: 7
 Server Version: 19.03.0-rc3
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 4.19.42-v7+
 Operating System: Raspbian GNU/Linux 9 (stretch)
 OSType: linux
 Architecture: armv7l
 CPUs: 4
 Total Memory: 926.1MiB
 Name: raspberrypi
 ID: SJG3:SBJ2:7E63:4KEV:SJNJ:6HXM:UX2S:XOOT:MN6D:2WTM:NBBT:FNIP
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No swap limit support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support

Additional environment details (AWS, VirtualBox, physical, etc.):

raspberry pi

Either this is limited to armhf, or this is only in RC3 and not in RC2.

@tiborvass also hinted at:

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 5
  • Comments: 27 (9 by maintainers)

Most upvoted comments

For people who is lead to this page after searching with the error message, please upgrade the version of Docker >= 19.03.8.

I am seeing same error with ‘docker cp’ on 19.03.5 in Ubuntu 18.04.

Thanks for all your help, I’ll take this one. Will report back.

Yes, I think the cause was identified; we’re looking at the right fix (there’s a couple of options being discussed)

Upgrading to Docker version 19.03.8 fixed this for me