Failed to register layer error processing tar file

Description
I’m using docker on windows 7 via docker toolbox , when trying to pull a big image of 4 Go I get the following output
latest: Pulling from preintv2
50655cf8037a: Extracting [==================================================>] 4.055 GB/4.055 GB
failed to register layer: Error processing tar file(exit status 1): write file : no space left on device

What I find unusual is that when I type df -h :

$ df -h
Filesystem Size Used Avail Use% Mounted on
C:/Program Files/Git 239G 187G 52G 79% /
U: 3,0T 2,5T 494G 84% /u
V: 20G 8,4G 11G 44% /v
X: 14G 2,2G 11G 17% /x
Z: 16G 37K 16G 1% /z

in the partition /u the size is 3.0T I don’t know from where it comes , in my windows C:/ partition it remains only 80Go .

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

Output of docker version:

$ docker version
time="2017-04-25T15:39:42+02:00" level=info msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"
Client:
 Version:      17.03.1-ce
 API version:  1.27
 Go version:   go1.7.5
 Git commit:   c6d412e
 Built:        Tue Mar 28 00:40:02 2017
 OS/Arch:      windows/amd64

Server:
 Version:      17.04.0-ce
 API version:  1.28 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   4845c56
 Built:        Wed Apr  5 18:45:47 2017
 OS/Arch:      linux/amd64
 Experimental: false

Output of docker info:

$ docker info
time="2017-04-25T15:22:02+02:00" level=info msg="Unable to use system certificate pool: crypto/x509: system root pool is not available on Windows"
Containers: 6
 Running: 0
 Paused: 0
 Stopped: 6
Images: 2
Server Version: 17.04.0-ce
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 26
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary:
containerd version: 422e31ce907fd9c3833a38d7b8fdd023e5a76e73
runc version: 9c2d8d184e5da67c95d601382adf14862e4f2228
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.4.59-boot2docker
Operating System: Boot2Docker 17.04.0-ce (TCL 7.2); HEAD : c69677f - Thu Apr  6 16:26:16 UTC 2017
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 995.8 MiB
Name: default
ID: CYXK:K7TN:O3OZ:SVML:FCLM:PLSB:SL4P:2ZF4:7VF2:H6UM:W2YI:FIW6
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 17
 Goroutines: 26
 System Time: 2017-04-25T13:22:02.240737949Z
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

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

I am trying to run Docker hello-world on armel platform. However, I am getting tar: invalid argument error as shown. I am Running Docker in chroot environment. Hoping to get some pointers…

#./docker run hello-world
DEBU[2019-05-27T13:59:01.403488020Z] Calling GET /_ping

DEBU[2019-05-27T13:59:01.406786120Z] Calling POST /v1.39/containers/create

DEBU[2019-05-27T13:59:01.407900660Z] form data: 
{"AttachStderr":true,"AttachStdin":false,"AttachStdout":true,"Cmd":null,"Domainname":"","Entrypoint":null,"Env":[],"HostConfig":{"AutoRemove":false,"Binds":null,"BlkioDeviceReadBps":null,"BlkioDeviceReadIOps":null,"BlkioDeviceWriteBps":null,"BlkioDeviceWriteIOps":null,"BlkioWeight":0,"BlkioWeightDevice":[],"CapAdd":null,"CapDrop":null,"Cgroup":"","CgroupParent":"","ConsoleSize":[0,0],"ContainerIDFile":"","CpuCount":0,"CpuPercent":0,"CpuPeriod":0,"CpuQuota":0,"CpuRealtimePeriod":0,"CpuRealtimeRuntime":0,"CpuShares":0,"CpusetCpus":"","CpusetMems":"","DeviceCgroupRules":null,"Devices":[],"DiskQuota":0,"Dns":[],"DnsOptions":[],"DnsSearch":[],"ExtraHosts":null,"GroupAdd":null,"IOMaximumBandwidth":0,"IOMaximumIOps":0,"IpcMode":"","Isolation":"","KernelMemory":0,"Links":null,"LogConfig":{"Config":{},"Type":""},"MaskedPaths":null,"Memory":0,"MemoryReservation":0,"MemorySwap":0,"MemorySwappiness":-1,"NanoCpus":0,"NetworkMode":"default","OomKillDisable":false,"OomScoreAdj":0,"PidMode":"","PidsLimit":0,"PortBindings":{},"Privileged":false,"PublishAllPorts":false,"ReadonlyPaths":null,"ReadonlyRootfs":false,"RestartPolicy":{"MaximumRetryCount":0,"Name":"no"},"SecurityOpt":null,"ShmSize":0,"UTSMode":"","Ulimits":null,"UsernsMode":"","VolumeDriver":"","VolumesFrom":null},"Hostname":"","Image":"hello-world","Labels":{},"NetworkingConfig":{"EndpointsConfig":{}},"OnBuild":null,"OpenStdin":false,"StdinOnce":false,"Tty":false,"User":"","Volumes":{},"WorkingDir":""}

Unable to find image 'hello-world:latest' locally

DEBU[2019-05-27T13:59:01.413317800Z] Calling GET /v1.39/info

WARN[2019-05-27T13:59:01.414791760Z] Could not get operating system name: Error opening /usr/lib/os-release: open /usr/lib/os-release: no such file or directory

DEBU[2019-05-27T13:59:01.438037600Z] Calling POST /v1.39/images/create?fromImage=hello-world&tag=latest

DEBU[2019-05-27T13:59:01.438664080Z] Trying to pull hello-world from https://registry-1.docker.io v2

DEBU[2019-05-27T13:59:02.340561960Z] Pulling ref from V2 registry: hello-world:latest

DEBU[2019-05-27T13:59:02.340799640Z] docker.io/library/hello-world:latest resolved to a manifestList object with 9 entries; looking for a unknown/arm match

DEBU[2019-05-27T13:59:02.340851620Z] found deprecated partial match for linux/arm/v8 with media type application/vnd.docker.distribution.manifest.v2+json, digest sha256:1e44d8bca6fb0464794555e5ccd3a32e2a4f6e44a20605e4e82605189904f44d
DEBU[2019-05-27T13:59:02.340898100Z] found deprecated partial match for linux/arm/v8 with media type application/vnd.docker.distribution.manifest.v2+json, digest sha256:d1fd2e204af0a2bca3ab033b417b29c76d7950ed29a44e427d1c4d07d14f04f9

DEBU[2019-05-27T13:59:02.340938600Z] found multiple matches in manifest list, choosing best match sha256:1e44d8bca6fb0464794555e5ccd3a32e2a4f6e44a20605e4e82605189904f44d
latest: Pulling from library/hello-world

DEBU[2019-05-27T13:59:02.498004860Z] pulling blob "sha256:590e13f69e4afcc08e9060a320ec5e4622d2771ace9dc26b024dc786fcb5b36e"
590e13f69e4a: Downloading 1.027kB/1.027kB
590e13f69e4a: Extracting 1.027kB/1.027kB
590e13f69e4a: Extracting 1.027kB/1.027kB

DEBU[2019-05-27T13:59:03.433254360Z] Cleaning up layer 22e8d4d817b6220a7884a028ba7b1e52b09f83b760a34acc3b9ffaf07f1f4cc4: Error processing tar file(exit status 1): invalid argument

INFO[2019-05-27T13:59:03.434607560Z] Attempting next endpoint for pull after error: failed to register layer: Error processing tar file(exit status 1): invalid argument

./docker: failed to register layer: Error processing tar file(exit status 1): invalid argument.

See './docker run --help'.

#./docker info
DEBU[2019-05-27T14:15:14.212268660Z] Calling GET /_ping

DEBU[2019-05-27T14:15:14.213233780Z] Calling GET /v1.39/info

WARN[2019-05-27T14:15:14.214784160Z] Could not get operating system name: Error opening /usr/lib/os-release: open /usr/lib/os-release: no such file or directory

Containers: 0

Running: 0

Paused: 0

Stopped: 0

Images: 0

Server Version: 18.09.4

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 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: bb71b10fd8f58240ca47fbb579b9d1028eea7c84

runc version: 2b18fe1d885ee5083ef9f0838fee39b62d653e30

init version: fec3683

Kernel Version: 4.1.51-ws-symbol

OSType: linux

Architecture: aarch64

CPUs: 2

Total Memory: 870.7MiB

Name: (none)

ID: AWJE:2XHF:F6IX:AFBY:RKSO:ZAD5:QORR:OWBG:RXWM:UHBC:24JT:PT55

Docker Root Dir: /mnt/usb/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: No cpu cfs quota support

WARNING: No cpu cfs period support

0

3

Using default tag: latest

latest: Pulling from vimagick/privoxy

8e3ba11ec2a2: Extracting 

[==================================================>]  

2.207MB/2.207MB

36c2a994d09d: Download complete 

821b025e6874: Download complete 

failed to register layer: Error processing tar file(exit 
status 1): invalid argument

ChrootDir=$1;

if [ -z $ChrootDir ]; then
{
        echo 'Please specify a non null $ChrootDir';
        exit 1;
}
fi;

bind_dir()
{                                                                                           
        DirName=$1;                                                                         
        MountPoint=$ChrootDir""$DirName;                                                    
        umount $MountPoint; >> /dev/null;                                                   
                                                                                            
        mkdir -p $MountPoint;                                                               
        mount --bind $DirName $MountPoint;                                                  
}                                                                                           


bind_file()
{
        FileName=$1;
        MountPoint=$ChrootDir""$FileName;
        umount $MountPoint; >> /dev/null;

        mount --bind $FileName $MountPoint;
}



bind_system()
{

        mkdir -p $ChrootDir/sys $ChrootDir/proc $ChrootDir/dev $ChrootDir/usr/src $ChrootDir/lib/modules $ChrootDir/utils $ChrootDir/download $ChrootDir/home $ChrootDir/var/run2;

        bind_dir /sys;
        bind_dir /proc;
        bind_dir /dev;
        bind_dir /dev/pts;
        bind_dir /usr/src;
        bind_dir /lib/modules;
        bind_dir /utils;

        bind_dir /download;
        bind_dir /home;
        bind_dir /var/run2/mysqld;



        bind_dir /data_root;
#       bind_dir /data_root/data/versions;
#       bind_dir /data_root/data/domains;

#       bind_file /etc/passwd;
#       bind_file /etc/group;
#       bind_file /etc/shadow;

        bind_file /etc/hosts;
        bind_file /etc/hostname;
        bind_file /etc/localtime;
        bind_file /etc/timezone;
        bind_file /etc/resolv.conf;
#       bind_file /root/.Xauthority;

}

bind_system;

When starting a container, you may see this error message:

failed to register layer: Error processing tar file (exit status 1): container id 1000000 cannot be mapped to a host id

This document explains the problem and how to fix it.

The user namespace (userns) is a feature of the Linux kernel that adds another security layer to Linux containers. The userns allows a host machine to run containers outside its UID/GID namespace. This means all containers can have a root account (UID 0) in their own namespace and run processes without receiving root privileges from the host machine.

When a userns is created, the Linux kernel provides a mapping between the container and the host machine. For example, if you start a container and run a process with UID 0 inside of it, the Linux kernel maps the container’s UID 0 to a non-privileged UID on the host machine. This allows the container to run a process as if it were the root user, while actually being run by the non-root user on the host machine.

The error is caused by a userns remapping failure. CircleCI runs Docker containers with userns enabled in order to securely run customers’ containers. The host machine is configured with a valid UID/GID for remapping. This UID/GID must be in the range of 0 — 65535.

When Docker starts a container, Docker pulls an image and extracts layers from that image. If a layer contains files with UID/GID outside of the accepted range, Docker cannot successfully remap and fails to start the container.

To fix this error, you must update the files’ UID/GID and re-create the image.

If you are not the image maintainer, congratulations: it’s not your responsibility. Contact the image maintainer and report the error.

If you are the image maintainer, identify the file with the high UID/GID and correct it. First, grab the high UID/GID from the error message. In the example presented at the top of this document, this value is 1000000. Next, start the container and look for the files which receive that invalid value.

Below is an example of finding an invalid file inside circleci/doc-highid using the find command:

# Start a shell inside the container
$ docker run -it circleci/doc-highid sh

# Find the file with high UID/GID
$ find / ( -uid 1000000 )  -ls 2>/dev/null
     50      0 -rw-r--r--   1 veryhigh veryhigh        0 Jul  9 03:05 /file-with-high-id

# Confirm that the file has high UID/GID
$ ls -ln file-with-high-id
-rw-r--r-- 1 1000000 1000000 0 Jul  9 03:05 file-with-high-id

After locating the offending file, change its ownership and re-create the image.

Note: It is possible for an invalid file to be generated and removed while a container is building. In this case, you may have to modify the RUN step in the Dockerfile itself. Adding && chown -R root:root /root to the problem step should fix the problem without creating a bad interim.

Refer to the following Microsoft forum post for additional links if you get more errors after performing this procedure.

Docker error processing tar file occurs due to insufficient space or due to permission issues.

Here at Bobcares, we have seen several causes for this error while troubleshooting Docker issues as part of our Docker Hosting Support.

Today we’ll take a look at the cause for this error and how to fix it.

Why does Docker error processing tar file occur

Now let’s see why does this Docker error occur.

Generally, this error occurs while running any command in the Docker. This occurs if there is no space left on the device.
Also, in some cases, we noticed that this error also arose when there were some permission issues with certain files.

However, the reason for this error differs accordingly.

For instance, the error appears as below.

How we fix Docker error processing tar file

Let’s move to the solution part of this error. Here are the cases where we resolved this error for our customers.

1. Remove unused images

Recently, one of our customers approached us with the same error. He was trying to clear the space from his device and ran into the below error.

ERROR: Error processing tar file(exit status 1): unexpected EOF.

Now, let’s see how our Support Engineers fix this error for our customers.

First, we used a built-in command to remove unused images (Version 1.13+)

docker image prune

Then we ran the below command to stop the Docker.

systemctl stop docker

After that, we backed up the docker folder /var/lib/docker and removed it by running the below command

NOTE: This will remove images, containers, volumes, … make sure you back it up first.

rm -rf /var/lib/docker

Once this is done, we started the Docker service by running the below command.

systemctl start docker

This, fixed the error.

2. Permission issue

In a few cases, we saw that the files owned by root in the directory having permission issues. Providing the files proper permissions fixed the issue. For that, we used the below command.

chown -R : /var/lib/docker/tmp

[Need any further assistance in fixing Docker errors? – We’re available 24*7]

Conclusion

In short, this Docker error occurs due to insufficient space or due to permission issues. Today, we saw how our Support Engineers resolve this error to our customers.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;