Error response from daemon error processing tar file exit status 1 unlinkat - Исправление ошибок и поиск оптимальных решений проблем

I needed space and executed: docker rmi $(docker images -f "dangling=true" -q)

Since then I can’t with docker-compose: docker-compose build, I get the error: ERROR: Error processing tar file(exit status 1): unexpected EOF.

I tried to remove all images, reinstall docker, but nothing will do: always the same error, after quite some time.

I built on another system and it worked, which suggests that this is a wrong-state issue.

Any idea what I should clean?

Using:

▶ docker version
Client:
 Version:      17.03.0-ce
 API version:  1.24 (downgraded from 1.26)
 Go version:   go1.7.5
 Git commit:   3a232c8
 Built:        Tue Feb 28 08:01:32 2017
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.6
 API version:  1.24 (minimum version )
 Go version:   go1.6.2
 Git commit:   78d1802
 Built:        Tue Jan 31 23:35:14 2017
 OS/Arch:      linux/amd64
 Experimental: false

▶ docker-compose version
docker-compose version 1.11.2, build dfed245
docker-py version: 2.1.0
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.0.1t  3 May 2016

asked Mar 14, 2017 at 11:11

I had the same issue and the approved answer didn’t work for me.

Turns out I had a file with permissions which didn’t allow the user running docker-compose to read it. After removing the file everything was OK

answered Jul 11, 2017 at 15:16

There is an built in command to remove unused images (Version 1.13+):

docker image prune

Now to handle the situation:

Stop Docker Service
```
systemctl stop docker
```
Backup /var/lib/docker then:
Remove /var/lib/docker
Caution: This will remove images, containers, volumes, … make sure you back it up first.
```
rm -rf /var/lib/docker
```
Start Docker service
```
systemctl start docker  
```

Update:

As noted in the other answer, In somecases it might be file permissions issue. Please review permissions.

answered Mar 14, 2017 at 12:16

Farhad FarahiFarhad Farahi

33.7k7 gold badges75 silver badges69 bronze badges

For me it was a permission error.
I walked against the same exact issue as PR,
ERROR: Error processing tar file(exit status 1): unexpected EOF
My solution is dirty but worked for me

chown -R 777 /foo/bar/project

You almost always want to avoid to set permissions on 777, 655 is more reasonable.

0 = ---
1 = --x
2 = -w-
3 = -wx
4 = r-
5 = r-x
6 = rw-
7 = rwx

A more detailed explanation can be found here:
https://www.pluralsight.com/blog/it-ops/linux-file-permissions

answered Dec 26, 2018 at 1:44

0x78f19350x78f1935

4056 silver badges10 bronze badges

Solving this error for good

docker build needs read access to every file in the context directory tree. To avoid permission issues, add all your mounted directories to .dockerignore file except those required for the build. For example, for this docker-compose file:

version: '3'
services:
    myservice:
        build: .
    volumes:
        - './etc:/etc/myservice'
        - './log:/var/log/myservice'

Add a .dockerignore file with this content:

/etc
/log

The problem will go away no matter the permissions of the files in your mounted directories.

How to get a more informative error

The docker-compose error is not very informative so you can try to run docker on each build just to get detailed information:

$ docker build .

You will get an error like this:

error checking context: 'no permission to read from '/home/david/docker/myservice/log/2020161.log'.

answered Jun 9, 2020 at 13:27

DavidDavid

2,84231 silver badges16 bronze badges

For me the issue turned out that a Docker Pull was hung, so I CTRL+C’d out of it and tried again. Same error message.

In the end I found some files owned by root in this directory. Giving the files proper permissions fixed the issue.

chown -R <username>:<group> /var/lib/docker/tmp

MAC Docker version 17.12.0-ce, build c97c6d6

answered Feb 14, 2018 at 2:42

there could be several different problems. You can find out the problem by checking the issue that docker build is throwing.

The problem is that docker-compose build will suppress the information of the issue. To find out what the issue is

do not use:

docker-compose build XXX

instead, open your docker-compose.yml, find the build: tag of the service is giving you an issue, e.g.

services:
   yourservice: 
       build: yourservice-directory/

and then run:

docker build yourservice-directory

after this you will see what is the issue.

Pang

9,354146 gold badges85 silver badges121 bronze badges

answered Jan 28, 2020 at 7:30

uselessuseless

1,84217 silver badges16 bronze badges

answered Jan 24, 2019 at 20:10

Padmini CPadmini C

1191 silver badge3 bronze badges

If you have tried looking through permissions, docker reset, docker system prune, deleting all containers, deleting all images (dangling or otherwise), reading about everything that there is surrounding this issue and have had no success. Try uninstalling docker and re-installing the stable version.

Although, the error I was struggling with was : Error processing tar file(exit status 1): mkdir /some/path/name: no such file or directory

answered Mar 15, 2018 at 15:42

Sheetal KaulSheetal Kaul

2,8992 gold badges13 silver badges6 bronze badges

In my case, the problem was a .dump file created by one of my project’s scripts.

docker-compose passes the context to the engine as a tar file, therefore, the build command was packing a tar (the .dump file) inside another tar file (the docker context) hence throwing an unexpected EOF on the context.

Since I don’t need the .dump file in the container, I added it to my .dockerignore file.

answered Sep 11, 2018 at 20:14

I was having the same issue when i changed the Dockerfile location in a python project. I tried the accepted answer and didn’t work for me.

I resolved the problem by running :

find . | grep -E "(__pycache__|.pyc|.pyo$)" | xargs sudo rm -r

On the project root.

The problem was that docker-compose build was trying to read files inside pycache folders.

Maybe this also can be fixed with a proper use of .dockerignore but i dind’t try it

Hope this helps.

Saludos.

answered Nov 26, 2019 at 17:45

Try increasing the memory for Docker, it fixed the issue for me.

Docker memory setting in Preferences was set to 2GB, so when pulling the ~3GB image, I was getting exactly this error:

$ docker pull skymindops/skil-ce
latest: Pulling from skymindops/skil-ce
118c5f2883d6: Pull complete 
3d199b2e6224: Extracting [==================================================>]  2.902GB/2.902GB
failed to register layer: Error processing tar file(exit status 1): unexpected EOF

Increasing the memory limit fixed it (I also increased the swap, but unsure was it required or not).

answered Apr 5, 2018 at 10:39

RostyRosty

1195 bronze badges

I tried everything from rebooting, reinstalling Docker, and purging /var/lib/docker.

My cause was something corrupting the build context in my project. After I ran git clean to reset the project directory back to its original state, I was able to docker-compose.

Run git clean -iXd in your project’s root to interactively git clean.

Edit: after a while, it happened again. This time, git clean didn’t fix it. I’m pretty sure it only happens on Ubuntu. My arch coworkers have never encountered it.

answered Aug 1, 2019 at 17:16

I found a temporary solution:

Ensure specify the image name on docker-compose.yml
for example, specify the image name and container_name as django_practice_db/django_practice_web

services:
  django_practice_db:
    image: postgres
    container_name: django_practice_db
  django_practice_web:
    container_name: django_practice_web
    build: .
    command: pipenv run python manage.py runserver 0.0.0.0:8000

Copy the project file to another place
Go inside the copied project directory
Execute docker-compose build
Go back to the original project directory
Execute docker-compose up

Not sure why I can build images when I change the folder path.

Pang

9,354146 gold badges85 silver badges121 bronze badges

answered Oct 12, 2019 at 5:51

Kant ChenKant Chen

1231 silver badge6 bronze badges

Another potential cause of this, especially if you’re seeing an error like

Error processing tar file(exit status 1): write /code/node_modules/xxx: no space left on device

You might want to check the «disk image size» in the Docker application. You might need to increase the disk size.

answered Feb 5, 2021 at 13:55

Nik BarresNik Barres

5231 gold badge8 silver badges18 bronze badges

I had the same error in Ubuntu: Ran below command and it worked (just make sure to start again once you are done):

/opt/McAfee/ens/tp/init/mfetpd-control.sh stop

answered Mar 1, 2021 at 7:00

Solve for me. You need have your user in docker group (usermod -aG docker $USER):

sudo chmod -R 775 .
sudo chown -R : .

answered Jun 13, 2021 at 10:57

makiolomakiolo

1761 silver badge4 bronze badges

This question is a little bit old now, but I had this problem today and what I figured out was next. When I was exporting my image as a tar file with next command:

docker save -o exportedfile.tar myimage/version:latest

I exported this in Linux shell instead of CMD. When I do it in CMD everything works fine. I guess there is some difference in -o flag between Windows and Linux.

answered Aug 23, 2022 at 13:59

RyukoteRyukote

7371 gold badge9 silver badges25 bronze badges

For me, I replaced the .tar file and tried to build again and it worked.

answered Nov 21, 2022 at 1:09

I had the same issue as OP, but neither the approved answer nor the top voted answer did it for me.

What pointed me in the right direction was a comment under the approved answer by JGlass saying that after closing Notepad++ everything worked properly.

I wasn’t using Notepad++, but I did have Visual Studio open. I didn’t have any files open either, but I did have the project open in the solution explorer. After closing Visual Studio, the issue was resolved.

In my case it wasn’t a permission issue, but Docker was unable to access the file because another application was using it.

Hopes this helps someone.

answered Jan 30 at 17:13

Источник

Description
I m trying to build an image for our Application. This is known to work as it was tested by our Developers.

Steps to reproduce the issue:

Place all artifacts to build the application image
Run the build process.

Describe the results you received:

[opc@siebel-docker-instance build]$ bash build-all-base 17.0np registry.local.com:5000 siebel registry.local.com:5000/oracle/database-instantclient/32bit:12.2.0.1 2>&1 | tee build.$(date +%F_%R).log                                                                                                                                                                   Beginning build for 17.0np                                                                                                                                                                                Mon May 27 13:30:18 GMT 2019                                                                                                                                                                              ...                                                                                                                                                                                                       Building sai element for 17.0np                                                                                                                                                                           ...                                                                                                                                                                                                       Sending build context to Docker daemon  3.203GB                                                                                                                                                           Error response from daemon: Error processing tar file(exit status 1): write /Siebel_Enterprise_Server/Disk1/stage/langs/de/Disk1/stage/Components/ses.siebel.si                                           ebsrvr.de/17.0.0.0.0/1/DataFiles/filegroup3.jar: no space left on device                                                                                                                                  Total reclaimed space: 0B                                                                                                                                                                                 ...                                                                                                                                                                                                       Building cgw element for 17.0np                                                                                                                                                                           ...                                                                                                                                                                                                       Sending build context to Docker daemon  3.203GB                                                                                                                                                           Error response from daemon: Error processing tar file(exit status 1): write /Siebel_Enterprise_Server/Disk1/stage/langs/de/Disk1/stage/Components/ses.siebel.si                                           ebsrvr.de/17.0.0.0.0/1/DataFiles/filegroup3.jar: no space left on device                                                                                                                                  Total reclaimed space: 0B                                                                                                                                                                                 ...                                                                                                                                                                                                       Building ses element for 17.0np                                                                                                                                                                           ...                                                                                                                                                                                                       Sending build context to Docker daemon  3.203GB                                                                                                                                                           Error response from daemon: Error processing tar file(exit status 1): write /Siebel_Enterprise_Server/Disk1/stage/langs/de/Disk1/stage/Components/ses.siebel.si                                           ebsrvr.de/17.0.0.0.0/1/DataFiles/filegroup3.jar: no space left on device                                                                                                                                  Total reclaimed space: 0B                                                                                                                                                                                 Mon May 27 13:33:42 GMT 2019                                                                                                                                                                              Build of 17.0np complete
--

Describe the results you expected:

This should create new images.

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

Output of docker version:

[opc@siebel-docker-instance build]$ docker version Client: Version: 18.09.1-ol API version: 1.39 Go version: go1.10.8 Git commit: c3ab8a8 Built: Mon Feb 11 23:20:32 2019 OS/Arch: linux/amd64 Experimental: false Server: Docker Engine — Community Engine: Version: 18.09.1-ol API version: 1.39 (minimum version 1.12) Go version: go1.10.8 Git commit: c3ab8a8 Built: Mon Feb 11 23:09:34 2019 OS/Arch: linux/amd64 Experimental: true Default Registry: docker.io

[opc@siebel-docker-instance build]$ docker info Containers: 33 Running: 0 Paused: 0 Stopped: 33 Images: 2 Server Version: 18.09.1-ol Storage Driver: overlay2 Backing Filesystem: xfs Supports d_type: true Native Overlay Diff: false 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: c4446665cb9c30056f4998ed953e6d4ff22c7c39 runc version: 4bb1fe4ace1a32d3676bb98f5d3b6a4e32bf6c58 init version: fec3683 Security Options: seccomp Profile: default selinux Kernel Version: 4.14.35-1844.4.5.el7uek.x86_64 Operating System: Oracle Linux Server 7.6 OSType: linux Architecture: x86_64 CPUs: 4 Total Memory: 29.18GiB Name: siebel-docker-instance ID: RUSM:322N:6JCV:NY7G:P3EL:UDS4:6SMQ:4JU6:YLJC:NIBF:SRC5:TYCE Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Registry: https://index.docker.io/v1/ Labels: Experimental: true Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false Product License: Community Engine Registries: docker.io (secure)

Additional environment details (AWS, VirtualBox, physical, etc.): OCI( Oracle Cloud Linux VM)

I added an additional disk — > /mnt/disk1

opc@siebel-docker-instance build]$ df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 15G 0 15G 0% /dev tmpfs 15G 0 15G 0% /dev/shm tmpfs 15G 49M 15G 1% /run tmpfs 15G 0 15G 0% /sys/fs/cgroup /dev/sda3 39G 36G 2.5G 94% / /dev/sda1 200M 9.7M 191M 5% /boot/efi tmpfs 3.0G 0 3.0G 0% /run/user/1000 /dev/sdb 1008G 77M 957G 1% /mnt/disk1

All permission are in place
[opc@siebel-docker-instance DataFiles]$ ls -ltr total 143272 -rwxrwxrwx. 1 opc opc 678 May 27 12:54 filegroup11.jar -rwxrwxrwx. 1 opc opc 10074 May 27 12:54 filegroup10.jar -rwxrwxrwx. 1 opc opc 252 May 27 12:54 filegroup1.jar -rwxrwxrwx. 1 opc opc 928 May 27 12:54 filegroup12.jar -rwxrwxrwx. 1 opc opc 13594 May 27 12:54 filegroup14.jar -rwxrwxrwx. 1 opc opc 711 May 27 12:54 filegroup15.jar -rwxrwxrwx. 1 opc opc 4563 May 27 12:54 filegroup13.jar -rwxrwxrwx. 1 opc opc 2392 May 27 12:54 filegroup16.jar -rwxrwxrwx. 1 opc opc 2353 May 27 12:54 filegroup18.jar -rwxrwxrwx. 1 opc opc 1084 May 27 12:54 filegroup19.jar -rwxrwxrwx. 1 opc opc 25411 May 27 12:54 filegroup17.jar -rwxrwxrwx. 1 opc opc 121785 May 27 12:54 filegroup2.jar -rwxrwxrwx. 1 opc opc 773 May 27 12:54 filegroup5.jar -rwxrwxrwx. 1 opc opc 2631 May 27 12:54 filegroup4.jar -rwxrwxrwx. 1 opc opc 3619 May 27 12:54 filegroup7.jar -rwxrwxrwx. 1 opc opc 1421 May 27 12:54 filegroup6.jar -rwxrwxrwx. 1 opc opc 76837 May 27 12:54 filegroup8.jar -rwxrwxrwx. 1 opc opc 2644 May 27 12:54 filegroup9.jar -rwxrwxrwx. 1 opc opc 146393727 May 27 12:54 filegroup3.jar

[opc@siebel-docker-instance build]$ docker system df TYPE TOTAL ACTIVE SIZE RECLAIMABLE Images 2 1 611.7MB 234.9MB (38%) Containers 33 0 17.08GB 17.08GB (100%) Local Volumes 0 0 0B 0B Build Cache 0 0 0B 0B

[opc@siebel-docker-instance build]$ docker images REPOSITORY TAG IMAGE ID CREATED SIZE registry.local.com:5000/oracle/database-instantclient/32bit 12.2.0.1 d41368fe502c 11 days ago 612MB oraclelinux latest 200d4182a980 6 weeks ago 235MB

Any suggestions as how to proceed next ?

Источник

Содержание

Docker Error Processing tar file – Quick solution
Why does Docker error processing tar file occur
How we fix Docker error processing tar file
1. Remove unused images
2. Permission issue
Conclusion
Are you using Docker based apps?
Error response from daemon: Error processing tar file(exit status 1): Total reclaimed space: 0B #39273
Comments
[opc@siebel-docker-instance build]$ docker info Containers: 33 Running: 0 Paused: 0 Stopped: 33 Images: 2 Server Version: 18.09.1-ol Storage Driver: overlay2 Backing Filesystem: xfs Supports d_type: true Native Overlay Diff: false 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: c4446665cb9c30056f4998ed953e6d4ff22c7c39 runc version: 4bb1fe4ace1a32d3676bb98f5d3b6a4e32bf6c58 init version: fec3683 Security Options: seccomp Profile: default selinux Kernel Version: 4.14.35-1844.4.5.el7uek.x86_64 Operating System: Oracle Linux Server 7.6 OSType: linux Architecture: x86_64 CPUs: 4 Total Memory: 29.18GiB Name: siebel-docker-instance ID: RUSM:322N:6JCV:NY7G:P3EL:UDS4:6SMQ:4JU6:YLJC:NIBF:SRC5:TYCE Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Registry: https://index.docker.io/v1/ Labels: Experimental: true Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false Product License: Community Engine Registries: docker.io (secure)
opc@siebel-docker-instance build]$ df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 15G 0 15G 0% /dev tmpfs 15G 0 15G 0% /dev/shm tmpfs 15G 49M 15G 1% /run tmpfs 15G 0 15G 0% /sys/fs/cgroup /dev/sda3 39G 36G 2.5G 94% / /dev/sda1 200M 9.7M 191M 5% /boot/efi tmpfs 3.0G 0 3.0G 0% /run/user/1000 /dev/sdb 1008G 77M 957G 1% /mnt/disk1
All permission are in place [opc@siebel-docker-instance DataFiles]$ ls -ltr total 143272 -rwxrwxrwx. 1 opc opc 678 May 27 12:54 filegroup11.jar -rwxrwxrwx. 1 opc opc 10074 May 27 12:54 filegroup10.jar -rwxrwxrwx. 1 opc opc 252 May 27 12:54 filegroup1.jar -rwxrwxrwx. 1 opc opc 928 May 27 12:54 filegroup12.jar -rwxrwxrwx. 1 opc opc 13594 May 27 12:54 filegroup14.jar -rwxrwxrwx. 1 opc opc 711 May 27 12:54 filegroup15.jar -rwxrwxrwx. 1 opc opc 4563 May 27 12:54 filegroup13.jar -rwxrwxrwx. 1 opc opc 2392 May 27 12:54 filegroup16.jar -rwxrwxrwx. 1 opc opc 2353 May 27 12:54 filegroup18.jar -rwxrwxrwx. 1 opc opc 1084 May 27 12:54 filegroup19.jar -rwxrwxrwx. 1 opc opc 25411 May 27 12:54 filegroup17.jar -rwxrwxrwx. 1 opc opc 121785 May 27 12:54 filegroup2.jar -rwxrwxrwx. 1 opc opc 773 May 27 12:54 filegroup5.jar -rwxrwxrwx. 1 opc opc 2631 May 27 12:54 filegroup4.jar -rwxrwxrwx. 1 opc opc 3619 May 27 12:54 filegroup7.jar -rwxrwxrwx. 1 opc opc 1421 May 27 12:54 filegroup6.jar -rwxrwxrwx. 1 opc opc 76837 May 27 12:54 filegroup8.jar -rwxrwxrwx. 1 opc opc 2644 May 27 12:54 filegroup9.jar -rwxrwxrwx. 1 opc opc 146393727 May 27 12:54 filegroup3.jar
[opc@siebel-docker-instance build]$ docker system df TYPE TOTAL ACTIVE SIZE RECLAIMABLE Images 2 1 611.7MB 234.9MB (38%) Containers 33 0 17.08GB 17.08GB (100%) Local Volumes 0 0 0B 0B Build Cache 0 0 0B 0B
[opc@siebel-docker-instance build]$ docker images REPOSITORY TAG IMAGE ID CREATED SIZE registry.local.com:5000/oracle/database-instantclient/32bit 12.2.0.1 d41368fe502c 11 days ago 612MB oraclelinux latest 200d4182a980 6 weeks ago 235MB
failed to copy files: failed to copy directory: Error processing tar file(exit status 1): write * no space left on device #38234
Comments
Error processing tar file(exit status 1): write /usr/libexec/gcc/x86_64-alpine-linux-musl/6.4.0/lto1: no space left on device #2
Comments
Footer
ОШИБКА Docker: ошибка обработки tar-файла (статус выхода 1): неожиданный EOF
Устранение этой ошибки навсегда
Как получить более информативную ошибку

Docker Error Processing tar file – Quick solution

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+)

Then we ran the below command to stop the 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.

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

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.

[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.

Are you using Docker based apps?

There are proven ways to get even more out of your Docker containers! Let us help you.

Spend your time in growing business and we will take care of Docker Infrastructure for you.

Источник

Error response from daemon: Error processing tar file(exit status 1): Total reclaimed space: 0B #39273

Description
I m trying to build an image for our Application. This is known to work as it was tested by our Developers.

Steps to reproduce the issue:

Place all artifacts to build the application image
Run the build process.

Describe the results you received:

Describe the results you expected:

This should create new images.

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

Output of docker version :

[opc@siebel-docker-instance build]$ docker info Containers: 33 Running: 0 Paused: 0 Stopped: 33 Images: 2 Server Version: 18.09.1-ol Storage Driver: overlay2 Backing Filesystem: xfs Supports d_type: true Native Overlay Diff: false 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: c4446665cb9c30056f4998ed953e6d4ff22c7c39 runc version: 4bb1fe4ace1a32d3676bb98f5d3b6a4e32bf6c58 init version: fec3683 Security Options: seccomp Profile: default selinux Kernel Version: 4.14.35-1844.4.5.el7uek.x86_64 Operating System: Oracle Linux Server 7.6 OSType: linux Architecture: x86_64 CPUs: 4 Total Memory: 29.18GiB Name: siebel-docker-instance ID: RUSM:322N:6JCV:NY7G:P3EL:UDS4:6SMQ:4JU6:YLJC:NIBF:SRC5:TYCE Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Registry: https://index.docker.io/v1/ Labels: Experimental: true Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false Product License: Community Engine Registries: docker.io (secure)

Additional environment details (AWS, VirtualBox, physical, etc.): OCI( Oracle Cloud Linux VM)

I added an additional disk — > /mnt/disk1

opc@siebel-docker-instance build]$ df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 15G 0 15G 0% /dev tmpfs 15G 0 15G 0% /dev/shm tmpfs 15G 49M 15G 1% /run tmpfs 15G 0 15G 0% /sys/fs/cgroup /dev/sda3 39G 36G 2.5G 94% / /dev/sda1 200M 9.7M 191M 5% /boot/efi tmpfs 3.0G 0 3.0G 0% /run/user/1000 /dev/sdb 1008G 77M 957G 1% /mnt/disk1

All permission are in place
[opc@siebel-docker-instance DataFiles]$ ls -ltr total 143272 -rwxrwxrwx. 1 opc opc 678 May 27 12:54 filegroup11.jar -rwxrwxrwx. 1 opc opc 10074 May 27 12:54 filegroup10.jar -rwxrwxrwx. 1 opc opc 252 May 27 12:54 filegroup1.jar -rwxrwxrwx. 1 opc opc 928 May 27 12:54 filegroup12.jar -rwxrwxrwx. 1 opc opc 13594 May 27 12:54 filegroup14.jar -rwxrwxrwx. 1 opc opc 711 May 27 12:54 filegroup15.jar -rwxrwxrwx. 1 opc opc 4563 May 27 12:54 filegroup13.jar -rwxrwxrwx. 1 opc opc 2392 May 27 12:54 filegroup16.jar -rwxrwxrwx. 1 opc opc 2353 May 27 12:54 filegroup18.jar -rwxrwxrwx. 1 opc opc 1084 May 27 12:54 filegroup19.jar -rwxrwxrwx. 1 opc opc 25411 May 27 12:54 filegroup17.jar -rwxrwxrwx. 1 opc opc 121785 May 27 12:54 filegroup2.jar -rwxrwxrwx. 1 opc opc 773 May 27 12:54 filegroup5.jar -rwxrwxrwx. 1 opc opc 2631 May 27 12:54 filegroup4.jar -rwxrwxrwx. 1 opc opc 3619 May 27 12:54 filegroup7.jar -rwxrwxrwx. 1 opc opc 1421 May 27 12:54 filegroup6.jar -rwxrwxrwx. 1 opc opc 76837 May 27 12:54 filegroup8.jar -rwxrwxrwx. 1 opc opc 2644 May 27 12:54 filegroup9.jar -rwxrwxrwx. 1 opc opc 146393727 May 27 12:54 filegroup3.jar

[opc@siebel-docker-instance build]$ docker system df TYPE TOTAL ACTIVE SIZE RECLAIMABLE Images 2 1 611.7MB 234.9MB (38%) Containers 33 0 17.08GB 17.08GB (100%) Local Volumes 0 0 0B 0B Build Cache 0 0 0B 0B

[opc@siebel-docker-instance build]$ docker images REPOSITORY TAG IMAGE ID CREATED SIZE registry.local.com:5000/oracle/database-instantclient/32bit 12.2.0.1 d41368fe502c 11 days ago 612MB oraclelinux latest 200d4182a980 6 weeks ago 235MB

Any suggestions as how to proceed next ?

The text was updated successfully, but these errors were encountered:

Источник

failed to copy files: failed to copy directory: Error processing tar file(exit status 1): write * no space left on device #38234

I am receiving the no space on disk error over and over.
docker info
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 4
Server Version: 18.03.1-ol
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: 773c489c9c1b21a6d78b5c538cd395416ec50f88
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: 949e6fa
Security Options:
seccomp
Profile: default
Kernel Version: 3.10.0-862.14.4.el7.x86_64
Operating System: Oracle Linux Server 7.5
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 15.51GiB
Name: dcmidavbrd4033
ID: XWYQ:2MB3:THRE:PKGN:S66Y:CT35:AOQC:4V5C:GWAH:JTOW:ZDRQ:FMV6
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 19
Goroutines: 32
System Time: 2018-11-20T14:38:37.512002321-05:00
EventsListeners: 0
Registry: https://index.docker.io/v1/
Labels:
Experimental: true
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
Registries: docker.io (secure)

docker system df
TYPE TOTAL ACTIVE SIZE RECLAIMABLE
Images 3 0 494.4MB 494.4MB (100%)
Containers 0 0 0B 0B
Local Volumes 0 0 0B 0B
Build Cache 0B 0B

I tried editing the config with simialr parameters but service wont start afterwards: ExecStart=/usr/bin/dockerd —graph=»/mnt/docker-data» —storage-driver=overlay —storage-opt=dm.basesize=30G

The text was updated successfully, but these errors were encountered:

Источник

Error processing tar file(exit status 1): write /usr/libexec/gcc/x86_64-alpine-linux-musl/6.4.0/lto1: no space left on device #2

Windows 10 Pro
Docker 17.12.0-ce-win47

Build error message as follow

Step 7/40 : RUN apk —no-cache —update add —virtual .builddeps.bazel bash build-base linux-headers python openjdk8 wget zip
—> Running in 995ca00b30c2
fetch http://dl-cdn.alpinelinux.org/alpine/v3.7/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.7/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.7/community/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.7/community/x86_64/APKINDEX.tar.gz
(1/70) Upgrading musl (1.1.18-r2 -> 1.1.18-r3)
(2/70) Installing pkgconf (1.3.10-r0)
(3/70) Installing ncurses-terminfo-base (6.0_p20171125-r0)
(4/70) Installing ncurses-terminfo (6.0_p20171125-r0)
(5/70) Installing ncurses-libs (6.0_p20171125-r0)
(6/70) Installing readline (7.0.003-r0)
(7/70) Installing bash (4.4.19-r1)
Executing bash-4.4.19-r1.post-install
(8/70) Installing binutils-libs (2.28-r3)
(9/70) Installing binutils (2.28-r3)
(10/70) Installing gmp (6.1.2-r1)
(11/70) Installing isl (0.18-r0)
(12/70) Installing libgomp (6.4.0-r5)
(13/70) Installing libatomic (6.4.0-r5)
(14/70) Installing libgcc (6.4.0-r5)
(15/70) Installing mpfr3 (3.1.5-r1)
(16/70) Installing mpc1 (1.0.3-r1)
(17/70) Installing libstdc++ (6.4.0-r5)
(18/70) Installing gcc (6.4.0-r5)
(19/70) Installing musl-dev (1.1.18-r3)
(20/70) Installing libc-dev (0.7.1-r0)
(21/70) Installing g++ (6.4.0-r5)
(22/70) Installing make (4.2.1-r0)
(23/70) Installing fortify-headers (0.9-r0)
(24/70) Installing build-base (0.5-r0)
(25/70) Installing linux-headers (4.4.6-r2)
(26/70) Installing libbz2 (1.0.6-r6)
(27/70) Installing expat (2.2.5-r0)
(28/70) Installing libffi (3.2.1-r4)
(29/70) Installing gdbm (1.13-r1)
(30/70) Installing sqlite-libs (3.21.0-r0)
(31/70) Installing python2 (2.7.14-r2)
(32/70) Installing libtasn1 (4.12-r2)
(33/70) Installing p11-kit (0.23.2-r2)
(34/70) Installing p11-kit-trust (0.23.2-r2)
(35/70) Installing ca-certificates (20171114-r0)
(36/70) Installing java-cacerts (1.0-r0)
(37/70) Installing libxau (1.0.8-r2)
(38/70) Installing libbsd (0.8.6-r1)
(39/70) Installing libxdmcp (1.1.2-r4)
(40/70) Installing libxcb (1.12-r1)
(41/70) Installing libx11 (1.6.5-r1)
(42/70) Installing libxcomposite (0.4.4-r1)
(43/70) Installing libxext (1.3.3-r2)
(44/70) Installing libxi (1.7.9-r1)
(45/70) Installing libxrender (0.9.10-r2)
(46/70) Installing libxtst (1.2.3-r1)
(47/70) Installing alsa-lib (1.1.4.1-r2)
(48/70) Installing libpng (1.6.34-r1)
(49/70) Installing freetype (2.8.1-r2)
(50/70) Installing giflib (5.1.4-r1)
(51/70) Installing libjpeg-turbo (1.5.2-r0)
(52/70) Installing openjdk8-jre-lib (8.151.12-r0)
(53/70) Installing java-common (0.1-r0)
(54/70) Installing krb5-conf (1.0-r1)
(55/70) Installing libcom_err (1.43.7-r0)
(56/70) Installing keyutils-libs (1.5.10-r0)
(57/70) Installing libverto (0.3.0-r0)
(58/70) Installing krb5-libs (1.15.2-r1)
(59/70) Installing lcms2 (2.8-r1)
(60/70) Installing nspr (4.17-r0)
(61/70) Installing nss (3.34.1-r0)
(62/70) Installing pcsc-lite-libs (1.8.22-r0)
(63/70) Installing lksctp-tools (1.0.17-r0)
(64/70) Installing openjdk8-jre-base (8.151.12-r0)
(65/70) Installing openjdk8-jre (8.151.12-r0)
(66/70) Installing openjdk8 (8.151.12-r0)
(67/70) Installing wget (1.19.2-r1)
(68/70) Installing zip (3.0-r4)
(69/70) Installing .builddeps.bazel (0)
(70/70) Upgrading musl-utils (1.1.18-r2 -> 1.1.18-r3)
Executing busybox-1.27.2-r7.trigger
Executing ca-certificates-20171114-r0.trigger
Executing java-common-0.1-r0.trigger
OK: 307 MiB in 79 packages
Error processing tar file(exit status 1): write /usr/libexec/gcc/x86_64-alpine-linux-musl/6.4.0/lto1: no space left on device

The text was updated successfully, but these errors were encountered:

You’re probably running out of disk space allocated for Docker, hence the no space left on device error. I would check my Docker.qcow2 to see if it’s approaching limits and perhaps remove some unused images

For reference check this one docker/for-win#1042

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

ОШИБКА Docker: ошибка обработки tar-файла (статус выхода 1): неожиданный EOF

Мне потребовалось место и я выполнил: docker rmi $(docker images -f «dangling=true» -q)

С тех пор я не могу с Докером-композом: docker-compose build я получаю сообщение об ошибке: ERROR: Error processing tar file(exit status 1): unexpected EOF .

Я попытался удалить все изображения, переустановить докер, но ничего не поделаешь: через некоторое время всегда одна и та же ошибка.

Я построил другую систему, и она сработала, что говорит о том, что это проблема неправильного состояния.

Есть идеи, что я должен чистить?

У меня была такая же проблема, и утвержденный ответ мне не подошел.

Оказывается, у меня был файл с разрешениями, которые не позволяли пользователю, запустившему docker-compose, его прочитать. После удаления файла все было ОК

Есть встроенная команда для удаления неиспользуемых изображений (Версия 1.13+):

Теперь, чтобы справиться с ситуацией:

Остановить службу Docker

/var/lib/docker Затем сделайте резервную копию :

Удалить /var/lib/docker Внимание: Это позволит удалить изображения, контейнеры, объемы, . убедитесь , что вы его резервную копию первого.

Запустить службу Docker

Обновлять:

Как отмечено в другом ответе, в некоторых случаях это может быть проблема с правами доступа к файлам. Пожалуйста, проверьте разрешения.

Для меня это была ошибка разрешения. Я столкнулся с той же проблемой, что и PR, ERROR: Error processing tar file(exit status 1): unexpected EOF мое решение грязное, но сработало для меня

chown -R 777 /foo/bar/project

Вы почти всегда хотите избежать установки разрешений на 777, 655 более разумно.

Устранение этой ошибки навсегда

docker build требуется доступ для чтения к каждому файлу в дереве каталогов контекста. Чтобы избежать проблем с разрешениями, добавьте в файл .dockerignore все подключенные каталоги, кроме тех, которые использовались во время сборки. Например, для этого docker-compose файла:

Добавьте .dockerignore файл с таким содержанием:

Проблема исчезнет независимо от разрешений файлов в ваших смонтированных каталогах.

Как получить более информативную ошибку

docker-compose Ошибка не очень информативна , так что вы можете попробовать запустить docker на каждую сборке только , чтобы получить подробную информацию:

Вы получите такую ошибку:

могло быть несколько разных проблем. Вы можете выяснить проблему, проверив проблему, которую выдает docker build.

Проблема в том, что сборка docker-compose подавляет информацию о проблеме. Чтобы узнать, в чем проблема

вместо этого откройте свой docker-compose.yml, найдите, что тег build: службы вызывает проблему, например

а затем запустите:

после этого вы увидите, в чем проблема.

Для меня проблема оказалась в том, что Docker Pull завис, поэтому я CTRL + C отключился и попробовал снова. То же сообщение об ошибке.

В конце концов, я нашел в этом каталоге несколько файлов, принадлежащих пользователю root. Предоставление файлов надлежащих разрешений устранило проблему.

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

MAC Docker версии 17.12.0-ce, сборка c97c6d6

Если вы пытались просмотреть разрешения, сбросить настройки докеров, очистить систему докеров, удалить все контейнеры, удалить все изображения (висячие или другие), прочитать обо всем, что связано с этой проблемой, и у вас не было успеха. Попробуйте удалить докер и переустановить стабильную версию.

Хотя ошибка, с которой я боролся, была: Error processing tar file(exit status 1): mkdir /some/path/name: no such file or directory

В моем случае проблема заключалась в файле .dump, созданном одним из сценариев моего проекта.

docker-compose передает контекст движку в виде tar-файла, поэтому build команда упаковывала tar (файл .dump) в другой tar-файл (контекст докера), следовательно, вызывала неожиданный EOF в контексте.

Поскольку мне не нужен файл .dump в контейнере, я добавил его в свой файл .dockerignore.

1. Очистите контейнеры, образы, тома и сети. в вашей системе:
docker system prune —all —force —volumes
2. docker-compose up

У меня была такая же проблема, когда я изменил расположение Dockerfile в проекте python . Я попробовал принятый ответ, но у меня ничего не получилось.

Я решил проблему, запустив:

В корне проекта.

Проблема заключалась в том, что сборка docker-compose пыталась читать файлы внутри папок pycache .

Возможно, это также можно исправить с помощью правильного использования .dockerignore, но я не пробовал

Надеюсь это поможет.

Попробуйте увеличить память для Docker, это устранило проблему для меня.

Параметр памяти Docker в настройках был установлен на 2 ГБ, поэтому при извлечении образа размером

3 ГБ я получал именно такую ошибку:

Увеличение предела памяти исправило это (я также увеличил своп, но не был уверен, нужно это или нет).

Я пробовал все: от перезагрузки, переустановки Docker и очистки /var/lib/docker .

Моя причина была в том, что что-то повредило контекст сборки в моем проекте. После того, как я побежал git clean сбросить каталог проекта в исходное состояние, я смог docker-compose .

Запустите git clean -iXd в корне вашего проекта в интерактивном режиме git clean .

Изменить: через некоторое время это случилось снова. На этот раз git clean не исправил. Я почти уверен, что это происходит только в Ubuntu. Мои коллеги по арке никогда с этим не сталкивались.

Нашел временное решение:

Убедитесь, что укажите имя изображения, docker-compose.yml например, укажите имя изображения и имя_контейнера как django_practice_db / django_practice_web

Скопируйте файл проекта в другое место

Войдите в каталог скопированного проекта

Выполнять docker-compose build

Вернитесь в исходный каталог проекта

Выполнять docker-compose up

Не уверен, почему я могу создавать изображения, когда меняю путь к папке.

Источник

I am on Manjaro.

I keep getting:

failed to register layer: Error processing tar file(exit status 1): write /usr/lib/x86_64-linux-gnu/libvlccore.so.9.0.0: no space left on device

while downloading:

docker pull kdeneon/all

This is the output of df -H

Filesystem      Size  Used Avail Use% Mounted on
dev             2.6G     0  2.6G   0% /dev
run             2.6G  930k  2.6G   1% /run
/dev/dm-0        16G   11G  4.8G  69% /
tmpfs           2.6G   39M  2.6G   2% /dev/shm
tmpfs           2.6G     0  2.6G   0% /sys/fs/cgroup
tmpfs           2.6G   48M  2.6G   2% /tmp
/dev/dm-1        18G  631M   17G   4% /home
tmpfs           514M  4.1k  514M   1% /run/user/1000

I have even symlinked the images directory from /var/lib/docker/image to /home/newbie/docker/image. Since /home has only 4% usage.

ls -l /var/lib/docker/image
lrwxrwxrwx 1 root root   26 Mar  9 07:32 image -> /home/newbie/docker/image/

This has no effect.

What else can I do ? Why is this happening ?

asked Mar 9, 2020 at 2:24

The correct way to solve this problem is to move the docker data directory to another location where there is sufficient space. In my case this was my home partition.

To do that I had to create a daemon.json file in /etc/docker and add the following lines to it:

{
    "data-root": "/home/newbie/docker_data"
}

Then restart the docker service, if you are suing systemd this should be:

systemctl restart docker

answered Mar 11, 2020 at 10:54

ng.newbieng.newbie

1,0256 gold badges16 silver badges26 bronze badges

I was experiencing the same error on a Mac computer without Docker Desktop. And moving the docker data directory did not work for me.

This is what worked for me using minikube.

minikube stop && minikube delete // this is required
minikube start --memory=16384 --cpus=8 --disk-size='80000mb'
eval $(minikube docker-env)

Then try your docker pull... again.

answered Feb 17, 2022 at 22:04

Источник