search

docker / for-mac

Bug reports for Docker Desktop for Mac
https://www.docker.com/products/docker#/mac
2.44k stars 119 forks source link

dind pull image error:failed to register layer: Error processing tar file(exit status 1): function not implemented #3294

Closed ChaimHong closed 5 years ago

ChaimHong commented 6 years ago

Expected behavior

hi, all with docker in docker ,when i pull image happen. on host docker ,pull this image is normal!

docker in docker

Actual behavior

/ # docker pull multicloud/netcat Using default tag: latest latest: Pulling from multicloud/netcat 518dc1482465: Pull complete a3ed95caeb02: Pull complete 93d7fedd3fb3: Pull complete 69c732137df0: Extracting [==================================================>] 24.6MB/24.6MB 409b3bc43c2d: Download complete d3777acfb75b: Download complete af62a24f3fae: Download complete failed to register layer: Error processing tar file(exit status 1): function not implemented

Information

Diagnostic logs

Docker for Mac: 18.06.1-ce-mac73 (26764)

host docker

Containers: 9
 Running: 2
 Paused: 0
 Stopped: 7
Images: 223
Server Version: 18.06.1-ce
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 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.9.93-linuxkit-aufs
Operating System: Docker for Mac
OSType: linux
Architecture: x86_64
CPUs: 3
Total Memory: 3.855GiB
Name: linuxkit-025000000001
ID: YFYK:MFZR:XQRS:VRPG:TCZM:KYZW:MHQA:SRJX:ZUUR:BSKA:ZL7S:ZUO5
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 40
 Goroutines: 72
 System Time: 2018-10-26T10:29:33.784235564Z
 EventsListeners: 2
HTTP Proxy: gateway.docker.internal:3128
HTTPS Proxy: gateway.docker.internal:3129
Registry: https://index.docker.io/v1/
Labels:
Experimental: true
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

dind

/ # docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 2
Server Version: 18.06.1-ce
Storage Driver: overlay2
 Backing Filesystem: <unknown>
 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.9.93-linuxkit-aufs
Operating System: Alpine Linux v3.8 (containerized)
OSType: linux
Architecture: x86_64
CPUs: 3
Total Memory: 3.855GiB
Name: a1c5670e1b8a
ID: LB34:IJVZ:67LB:5CF2:7ZMY:JGEA:MQ7B:JBOX:WY34:W4HK:5RG2:LK3E
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

Steps to reproduce the behavior

  1. docker pull multicloud/netcat
ChaimHong commented 6 years ago

Backing Filesystem: <unknown> is normal ?

docker-robott commented 5 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale comment. Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle stale

docker-robott commented 4 years ago

Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle locked