entityMap|blocks|key|1ce76|text|有一个内置命令可以删除未使用的镜像(1.13%2B版)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|cnlal|docker+image+prune|code-block|syntax|javascript|269ol|现在来处理这种情况：|ebo4r|停止Docker服务|45eo2|systemctl停止docker|c2ii5|备份|7emkg|然后：|1f98j|删除|4kugk|注意:这将删除图像、容器、卷...请确保先备份它。|5kesm|rm+-rf+/var/lib/docker|5ss1q|启动Docker服务|4ub4q|systemctl启动docker|338a|更新：|1j0mj|正如在另一个答案中指出的，在某些情况下，这可能是文件权限问题。请检查权限。^0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|15|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|16|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|17|9|@]|A|@]|B|$]]|$2|J|4|K|6|7|8|18|9|@]|A|@]|B|$]]|$2|L|4|M|6|7|8|19|9|@]|A|@]|B|$]]|$2|N|4|O|6|7|8|1A|9|@]|A|@]|B|$]]|$2|P|4|Q|6|7|8|1B|9|@]|A|@]|B|$]]|$2|R|4|S|6|7|8|1C|9|@]|A|@]|B|$]]|$2|T|4|U|6|7|8|1D|9|@]|A|@]|B|$]]|$2|V|4|W|6|7|8|1E|9|@]|A|@]|B|$]]|$2|X|4|Y|6|7|8|1F|9|@]|A|@]|B|$]]|$2|Z|4|10|6|7|8|1G|9|@]|A|@]|B|$]]|$2|11|4|12|6|7|8|1H|9|@]|A|@]|B|$]]|$2|13|4|14|6|7|8|1I|9|@]|A|@]|B|$]]]]

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

<pre><code>docker image prune
</code></pre>

Now to handle the situation:

<ul>
<li>Stop Docker Service

<pre><code>systemctl stop docker
</code></pre></li>
<li>Backup <code>/var/lib/docker</code> then:</li>
<li>Remove <code>/var/lib/docker</code>
Caution: This will remove images, containers, volumes, ... make sure you back it up first.

<pre><code>rm -rf /var/lib/docker
</code></pre></li>
<li>Start Docker service 

<pre><code>systemctl start docker 
</code></pre></li>
</ul>

Update:

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

entityMap|blocks|key|4rm6k|text|我也遇到了同样的问题，但批准的答案对我不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|196mj|原来我有一个文件，它的权限不允许运行docker-compose的用户读取它。删除文件后，一切正常^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|E|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|F|9|@]|A|@]|B|$]]]]

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

entityMap|blocks|key|6mjqc|text|对于我来说，问题是Docker拉挂了，所以我按CTRL%2BC退出，然后再试一次。相同的错误信息。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|213hv|最后，我在这个目录中找到了一些root拥有的文件。为文件赋予适当的权限已修复此问题。|5p8o3|MAC+Docker版本17.12.0-ce，内部版本c97c6d6^0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|G|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|H|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|I|9|@]|A|@]|B|$]]]]

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.

<code>chown -R &lt;username&gt;:&lt;group&gt; /var/lib/docker/tmp</code>

<ul>
<li>MAC Docker version 17.12.0-ce, build c97c6d6</li>
</ul>

entityMap|blocks|key|6k62k|text|如果您尝试查看权限，docker重置，docker系统修剪，删除所有容器，删除所有图像(悬空或其他)，阅读围绕此问题的所有信息，但均未成功。尝试卸载docker并重新安装稳定版本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3ktqf|尽管如此，我一直在纠结的错误是：^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|E|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|F|9|@]|A|@]|B|$]]]]

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 : <code>Error processing tar file(exit status 1): mkdir /some/path/name: no such file or directory</code>

entityMap|blocks|key|4dea7|text|尝试为Docker增加内存，它为我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|36eep|Preferences中的Docker内存设置被设置为2+3GB，所以当我拉取~3+3GB的镜像时，我得到的正是这个错误：|7ghh|$+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|code-block|syntax|javascript|37ir3|增加内存限制解决了这个问题(我也增加了交换空间，但不确定是否需要)。^0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|L|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|M|9|@]|A|@]|B|$]]|$2|E|4|F|6|G|8|N|9|@]|A|@]|B|$H|I]]|$2|J|4|K|6|7|8|O|9|@]|A|@]|B|$]]]]

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: 

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

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

entityMap|blocks|key|c1o5h|text|在我的例子中，问题是由我的一个项目脚本创建的.dump文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|b9q14|将上下文作为tar文件传递给引擎，因此，|289tq|命令将tar+(+.dump文件)打包到另一个tar文件(+docker上下文)中，因此在上下文中抛出意外的EOF。|6ruuc|因为我不需要容器中的.dump文件，所以我将它添加到我的.dockerignore文件中。^0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|I|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|J|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|K|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|L|9|@]|A|@]|B|$]]]]

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

<code>docker-compose</code> passes the context to the engine as a tar file, therefore, the <code>build</code> 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.

entityMap|blocks|key|fr5t1|text|对我来说，这是一个权限错误。我反对和公关一样的问题，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|8l0av|我的解决方案很脏，但对我很有效|3to6n|您几乎总是希望避免在777，655上设置权限是更合理的。|bfpci|0+=+---
1+=+--x
2+=+-w-
3+=+-wx
4+=+r-
5+=+r-x
6+=+rw-
7+=+rwx|code-block|syntax|javascript|7r08k|更详细的解释可以在这里找到：|b3cc8|https://www.pluralsight.com/blog/it-ops/linux-file-permissions^0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|P|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|Q|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|R|9|@]|A|@]|B|$]]|$2|G|4|H|6|I|8|S|9|@]|A|@]|B|$J|K]]|$2|L|4|M|6|7|8|T|9|@]|A|@]|B|$]]|$2|N|4|O|6|7|8|U|9|@]|A|@]|B|$]]]]

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

<code>chown -R 777 /foo/bar/project</code>

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

<pre><code>0 = ---
1 = --x
2 = -w-
3 = -wx
4 = r-
5 = r-x
6 = rw-
7 = rwx
</code></pre>

A more detailed explanation can be found here:
<a href="https://www.pluralsight.com/blog/it-ops/linux-file-permissions" rel="noreferrer">https://www.pluralsight.com/blog/it-ops/linux-file-permissions</a>

entityMap|blocks|key|ef6va|text|参考资料：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5jnec|https://medium.com/the-code-review/clean-out-your-docker-images-containers-and-volumes-with-single-commands-b8e38253c271|23ork|amrov|清理系统上的容器、映像、卷和网络：|3v4d9|6s7qb|docker系统修剪--all+--force+--volumes|7j3t8|docker-compose+up^0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|M|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|N|9|@]|A|@]|B|$]]|$2|E|4|-4|6|7|8|O|9|@]|A|@]|B|$]]|$2|F|4|G|6|7|8|P|9|@]|A|@]|B|$]]|$2|H|4|-4|6|7|8|Q|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|R|9|@]|A|@]|B|$]]|$2|K|4|L|6|7|8|S|9|@]|A|@]|B|$]]]]

Reference:
<a href="https://medium.com/the-code-review/clean-out-your-docker-images-containers-and-volumes-with-single-commands-b8e38253c271" rel="nofollow noreferrer">https://medium.com/the-code-review/clean-out-your-docker-images-containers-and-volumes-with-single-commands-b8e38253c271</a>
 1. Clean up containers, images, volumes and networks on your system: 
docker system prune --all --force --volumes 
2. docker-compose up

entityMap|blocks|key|2hev7|text|我尝试了所有方法，从重新启动、重新安装Docker到清除|type|unstyled|depth|inlineStyleRanges|entityRanges|data|89pot|..。|c0ggr|我的原因是一些东西破坏了我的项目中的构建上下文。|jmta|在我跑完之后|318hn|要将项目目录重置回其原始状态，我能够|606ul|52oeh|运行|49j95|在项目根目录中以交互方式|7o05k|dicd6|编辑:过了一段时间，它又发生了。这一次，|bbis0|没修好。我很确定这只发生在Ubuntu上。我的同事从来没有遇到过这种情况。^0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|U|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|V|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|W|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|X|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|Y|9|@]|A|@]|B|$]]|$2|K|4|D|6|7|8|Z|9|@]|A|@]|B|$]]|$2|L|4|M|6|7|8|10|9|@]|A|@]|B|$]]|$2|N|4|O|6|7|8|11|9|@]|A|@]|B|$]]|$2|P|4|D|6|7|8|12|9|@]|A|@]|B|$]]|$2|Q|4|R|6|7|8|13|9|@]|A|@]|B|$]]|$2|S|4|T|6|7|8|14|9|@]|A|@]|B|$]]]]

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

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

Run <code>git clean -iXd</code> in your project's root to interactively <code>git clean</code>.

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

entityMap|blocks|key|ef7af|text|我找到了一个临时解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|734q7|确保在上指定映像名称|f93du|例如，指定镜像名称和容器|dgmnf|_|91pf2|名为django|6bms1|10c51|实践|8igvn|5scr4|db/django|embso|36b16|4tu66|37u8g|网站|abb85|服务:+django|9djkp|904n|86ei|1ivop|db:+image:+postgres容器|35mpp|3e8ki|姓名:+django|2hi6i|9edhv|fhh67|5h0md|db+django|834a0|2sad1|ch5pf|19c0g|web:容器|4avrj|fi0oh|姓名:+django|44n4v|dgtbb|3m35v|amhbp|web构建：。命令:+pipenv+run+python+manage.py+runserver+0.0.0.0:8000|73nnv|将项目文件复制到其他位置|308d|进入复制的项目目录|99no3|执行|ac03b|返回到原始项目目录|2pofc|dss3u|当我改变文件夹路径时，我不确定为什么我可以构建镜像。^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|1Y|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|1Z|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|20|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|21|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|22|9|@]|A|@]|B|$]]|$2|K|4|H|6|7|8|23|9|@]|A|@]|B|$]]|$2|L|4|M|6|7|8|24|9|@]|A|@]|B|$]]|$2|N|4|H|6|7|8|25|9|@]|A|@]|B|$]]|$2|O|4|P|6|7|8|26|9|@]|A|@]|B|$]]|$2|Q|4|H|6|7|8|27|9|@]|A|@]|B|$]]|$2|R|4|M|6|7|8|28|9|@]|A|@]|B|$]]|$2|S|4|H|6|7|8|29|9|@]|A|@]|B|$]]|$2|T|4|U|6|7|8|2A|9|@]|A|@]|B|$]]|$2|V|4|W|6|7|8|2B|9|@]|A|@]|B|$]]|$2|X|4|H|6|7|8|2C|9|@]|A|@]|B|$]]|$2|Y|4|M|6|7|8|2D|9|@]|A|@]|B|$]]|$2|Z|4|H|6|7|8|2E|9|@]|A|@]|B|$]]|$2|10|4|11|6|7|8|2F|9|@]|A|@]|B|$]]|$2|12|4|H|6|7|8|2G|9|@]|A|@]|B|$]]|$2|13|4|14|6|7|8|2H|9|@]|A|@]|B|$]]|$2|15|4|H|6|7|8|2I|9|@]|A|@]|B|$]]|$2|16|4|M|6|7|8|2J|9|@]|A|@]|B|$]]|$2|17|4|H|6|7|8|2K|9|@]|A|@]|B|$]]|$2|18|4|19|6|7|8|2L|9|@]|A|@]|B|$]]|$2|1A|4|H|6|7|8|2M|9|@]|A|@]|B|$]]|$2|1B|4|M|6|7|8|2N|9|@]|A|@]|B|$]]|$2|1C|4|H|6|7|8|2O|9|@]|A|@]|B|$]]|$2|1D|4|1E|6|7|8|2P|9|@]|A|@]|B|$]]|$2|1F|4|H|6|7|8|2Q|9|@]|A|@]|B|$]]|$2|1G|4|1H|6|7|8|2R|9|@]|A|@]|B|$]]|$2|1I|4|H|6|7|8|2S|9|@]|A|@]|B|$]]|$2|1J|4|M|6|7|8|2T|9|@]|A|@]|B|$]]|$2|1K|4|H|6|7|8|2U|9|@]|A|@]|B|$]]|$2|1L|4|1M|6|7|8|2V|9|@]|A|@]|B|$]]|$2|1N|4|1O|6|7|8|2W|9|@]|A|@]|B|$]]|$2|1P|4|1Q|6|7|8|2X|9|@]|A|@]|B|$]]|$2|1R|4|1S|6|7|8|2Y|9|@]|A|@]|B|$]]|$2|1T|4|1U|6|7|8|2Z|9|@]|A|@]|B|$]]|$2|1V|4|1S|6|7|8|30|9|@]|A|@]|B|$]]|$2|1W|4|1X|6|7|8|31|9|@]|A|@]|B|$]]]]

I found a temporary solution:
<ol>
<li>Ensure specify the image name on <code>docker-compose.yml</code>
for example, specify the image name and container_name as django_practice_db/django_practice_web
<pre class="lang-yaml prettyprint-override"><code>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
</code></pre>
</li>
<li>Copy the project file to another place
</li>
<li>Go inside the copied project directory
</li>
<li>Execute <code>docker-compose build</code>
</li>
<li>Go back to the original project directory
</li>
<li>Execute <code>docker-compose up</code>
</li>
</ol>
Not sure why I can build images when I change the folder path.

entityMap|blocks|key|dp59t|text|中更改Dockerfile位置时也遇到了同样的问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|533p9|python项目|1tush|..。我尝试了被接受的答案，但对我来说不起作用。|881do|我通过运行以下命令解决了这个问题：|a16pp|find+.+%7C+grep+-E+"(__pycache__%7C\.pyc%7C\.pyo$)"+%7C+xargs+sudo+rm+-r|code-block|syntax|javascript|9snru|在项目根目录上。|fjdrp|问题是docker-compose构建试图读取其中的文件|88qg1|pycache|5amqg|文件夹。|2dhvm|也许这也可以通过正确使用.dockerignore来修复，但我不会尝试它|9tdqq|希望这能有所帮助。|1ud7p|干杯。^0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|11|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|12|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|13|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|14|9|@]|A|@]|B|$]]|$2|I|4|J|6|K|8|15|9|@]|A|@]|B|$L|M]]|$2|N|4|O|6|7|8|16|9|@]|A|@]|B|$]]|$2|P|4|Q|6|7|8|17|9|@]|A|@]|B|$]]|$2|R|4|S|6|7|8|18|9|@]|A|@]|B|$]]|$2|T|4|U|6|7|8|19|9|@]|A|@]|B|$]]|$2|V|4|W|6|7|8|1A|9|@]|A|@]|B|$]]|$2|X|4|Y|6|7|8|1B|9|@]|A|@]|B|$]]|$2|Z|4|10|6|7|8|1C|9|@]|A|@]|B|$]]]]

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 :

<pre><code>find . | grep -E "(__pycache__|\.pyc|\.pyo$)" | xargs sudo rm -r
</code></pre>

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.

entityMap|blocks|key|91huv|text|可能有几个不同的问题。你可以通过检查docker+build抛出的问题来找出问题所在。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|7v27l|问题是docker-compose构建会抑制问题的信息。找出问题所在|30hah|请勿使用：|3ao51|docker-compose+build+XXX|code-block|syntax|javascript|2jflm|相反，打开docker-compose.yml，找到|8q3hd|构建：|4o85s|服务的标签给了你一个问题，例如|5ilft|services:
+++yourservice:+
+++++++build:+yourservice-directory/|bsmjb|然后运行：|3cp85|docker+build+yourservice-directory|2c4v4|在此之后，您将看到问题所在。^0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|Z|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|10|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|11|9|@]|A|@]|B|$]]|$2|G|4|H|6|I|8|12|9|@]|A|@]|B|$J|K]]|$2|L|4|M|6|7|8|13|9|@]|A|@]|B|$]]|$2|N|4|O|6|7|8|14|9|@]|A|@]|B|$]]|$2|P|4|Q|6|7|8|15|9|@]|A|@]|B|$]]|$2|R|4|S|6|I|8|16|9|@]|A|@]|B|$J|K]]|$2|T|4|U|6|7|8|17|9|@]|A|@]|B|$]]|$2|V|4|W|6|I|8|18|9|@]|A|@]|B|$J|K]]|$2|X|4|Y|6|7|8|19|9|@]|A|@]|B|$]]]]

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:
<pre><code>docker-compose build XXX
</code></pre>
instead, open your docker-compose.yml, find the build: tag of the service is giving you an issue, e.g.
<pre class="lang-yaml prettyprint-override"><code>services:
 yourservice: 
 build: yourservice-directory/
</code></pre>
and then run:
<pre><code>docker build yourservice-directory
</code></pre>
after this you will see what is the issue.

entityMap|blocks|key|8suan|text|永远解决这个错误|type|unstyled|depth|inlineStyleRanges|entityRanges|data|cio1i|需要对上下文目录树中的每个文件具有读取访问权限。要避免权限问题，请将所有已挂载的目录添加到|apv3|.dockerignore|cibqo|文件，除了在构建过程中使用的那些。例如，对于这个|3di4p|文件：|j78l|version:+'3'
services:
++++myservice:
++++++++build:+.
++++volumes:
++++++++-+'./etc:/etc/myservice'
++++++++-+'./log:/var/log/myservice'|code-block|syntax|javascript|e8nif|添加|8121l|包含此内容的文件：|d37ap|/etc
/log|e2m8o|无论挂载目录中文件的权限如何，问题都会消失。|7hrha|如何获取更具信息性的错误|diej7|The+The+The|ffrol|错误信息不是很丰富，因此您可以尝试运行|7nbb5|在每个版本上，只需获取详细信息：|dbedd|$+docker+build+.|82p9e|您将得到如下错误：|6av1o|error+checking+context:+'no+permission+to+read+from+'/home/david/docker/myservice/log/2020161.log'.^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|1B|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|1C|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|1D|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|1E|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|1F|9|@]|A|@]|B|$]]|$2|K|4|L|6|M|8|1G|9|@]|A|@]|B|$N|O]]|$2|P|4|Q|6|7|8|1H|9|@]|A|@]|B|$]]|$2|R|4|S|6|7|8|1I|9|@]|A|@]|B|$]]|$2|T|4|U|6|M|8|1J|9|@]|A|@]|B|$N|O]]|$2|V|4|W|6|7|8|1K|9|@]|A|@]|B|$]]|$2|X|4|Y|6|7|8|1L|9|@]|A|@]|B|$]]|$2|Z|4|10|6|7|8|1M|9|@]|A|@]|B|$]]|$2|11|4|12|6|7|8|1N|9|@]|A|@]|B|$]]|$2|13|4|14|6|7|8|1O|9|@]|A|@]|B|$]]|$2|15|4|16|6|M|8|1P|9|@]|A|@]|B|$N|O]]|$2|17|4|18|6|7|8|1Q|9|@]|A|@]|B|$]]|$2|19|4|1A|6|M|8|1R|9|@]|A|@]|B|$N|O]]]]

<h3>Solving this error for good</h3>
<code>docker build</code> needs read access to every file in the context directory tree. To avoid permission issues, add all your mounted directories to <a href="https://docs.docker.com/engine/reference/builder/#dockerignore-file" rel="nofollow noreferrer">.dockerignore</a> file except those used during the build. For example, for this <code>docker-compose</code> file:
<pre class="lang-yaml prettyprint-override"><code>version: '3'
services:
 myservice:
 build: .
 volumes:
 - './etc:/etc/myservice'
 - './log:/var/log/myservice'
</code></pre>
Add a <code>.dockerignore</code> file with this content:
<pre><code>/etc
/log
</code></pre>
The problem will go away no matter the permissions of the files in your mounted directories.
<h3>How to get a more informative error</h3>
The <code>docker-compose</code> error is not very informative so you can try to run <code>docker</code> on each build just to get detailed information:
<pre><code>$ docker build .
</code></pre>
You will get an error like this:
<pre><code>error checking context: 'no permission to read from '/home/david/docker/myservice/log/2020161.log'.
</code></pre>

entityMap|blocks|key|7p6hl|text|导致这种情况的另一个潜在原因，特别是当您看到如下错误时|type|unstyled|depth|inlineStyleRanges|entityRanges|data|a9kn0|Error+processing+tar+file(exit+status+1):+write+/code/node_modules/xxx:+no+space+left+on+device|code-block|syntax|javascript|2e1pr|您可能需要检查Docker应用程序中的“磁盘映像大小”。您可能需要增加磁盘大小。^0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|J|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|K|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|L|9|@]|A|@]|B|$]]]]

Another potential cause of this, especially if you're seeing an error like
<pre><code>Error processing tar file(exit status 1): write /code/node_modules/xxx: no space left on device
</code></pre>
You might want to check the &quot;disk image size&quot; in the Docker application. You might need to increase the disk size.

entityMap|blocks|key|4mu2b|text|我在Ubuntu中遇到了同样的错误:运行下面的命令，它工作了(只需确保在完成后重新启动)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4ee67|/opt/McAfee/ens/tp/init/mfetpd-control.sh+stop|code-block|syntax|javascript^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|I|9|@]|A|@]|B|$F|G]]]]

I had the same error in Ubuntu: Ran below command and it worked (just make sure to start again once you are done):
<pre><code>/opt/McAfee/ens/tp/init/mfetpd-control.sh stop
</code></pre>

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

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

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:

<pre><code>▶ 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
</code></pre>

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

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

 我需要空间并执行了： 从那时起，我不能使用docker-compose： ，我得到了错误： ..。 我试着删除所有镜像，重新安装docker，但什么也做不了:在相当长的一段时间后，总是出现相同的错误。 我建立在另一个系统上，它工作正常， 建议 这是一个错误的状态问题。 你知道我该清理什么吗？ 使用： ▶ docker...

问Docker错误:处理tar文件时出错(退出状态1)：意外EOF
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Docker错误:处理tar文件时出错(退出状态1)：意外EOFEN