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