blocks|key|1162690|text|Dockerfile中的复制指令将src中的文件复制到dest文件夹。看起来您要么丢失了file1、file2和file3，要么试图从错误的文件夹构建Dockerfile。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1162691|参考Dockerfile医生|1162692|此外，构建Dockerfile的命令应该类似于。|1162693|cd+into/the/folder/
docker+build+-t+sometagname+.|code-block|syntax|javascript|1162694|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/reference/builder/#copy^0|0|A|H|3|R|4|18|5|1E|5|1K|5|23|A|0|0|E|0|0|5|A|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]|$9|15|A|16|B|C]|$9|17|A|18|B|C]|$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1B|8|@]|D|@$9|1C|A|1D|1|1E]]|E|$]]|$1|H|3|I|5|6|7|1F|8|@$9|1G|A|1H|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|1I|8|@]|D|@]|E|$M|N]]|$1|O|3|-4|5|6|7|1J|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

The COPY instruction in the <code>Dockerfile</code> copies the files in <code>src</code> to the <code>dest</code> folder. Looks like you are either missing the <code>file1</code>, <code>file2</code> and <code>file3</code> or trying to build the <code>Dockerfile</code> from the wrong folder. 

<a href="https://docs.docker.com/reference/builder/#copy" rel="noreferrer">Refer Dockerfile Doc</a>

Also the command for building the <code>Dockerfile</code> should be something like.

<pre><code>cd into/the/folder/
docker build -t sometagname .
</code></pre>

blocks|key|551126|text|也要检查.dockerignore文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|551127|我知道这是个非常罕见的案子，但我在那提到过那个文件。|551128|entityMap^0|4|D|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

Do check the <code>.dockerignore</code> file too.

I know this is a very rare case, but I had that file mentioned there.

blocks|key|1162754|text|这可能是因为您将file1/file2/file3称为一个绝对路径，它不存在于构建上下文中，Docker只在构建上下文中搜索路径。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1162755|例如，如果使用COPY+/home/yourname/file1，Docker将其解释为${docker+build+working+directory}/home/yourname/file1，如果此处没有同名的文件，则不会引发文件或目录错误。|1162756|请参阅码头问题之一|1162757|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/docker/docker/issues/4592^0|8|5|E|5|K|5|0|7|P|18|1H|0|3|6|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|13|8|@]|D|@$9|14|A|15|1|16]]|E|$]]|$1|J|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

It is possibly caused by you are referring <code>file1</code>/<code>file2</code>/<code>file3</code> as an absolute path which is not in build context, Docker only searches the path in the build context.
E.g. if you use <code>COPY /home/yourname/file1</code>, Docker build interprets it as <code>${docker build working directory}/home/yourname/file1</code>, if no file with the same name here, no file or directory error is thrown.
Refer to <a href="https://github.com/docker/docker/issues/4592" rel="noreferrer">One of the docker issue</a>

blocks|key|1714650|text|似乎这些命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1714651|docker+build+-t+imagename+.|code-block|syntax|javascript|1714652|以及：|1714653|docker+build+-t+imagename+-+<+Dockerfile2|1714654|不是以同样的方式执行的。如果您想使用Dockerfile和Dockerfile2从一个文件夹中构建2个对接者图像，那么在第二个使用stdin+(<+Dockerfile2)的示例中不能使用COPY命令。相反，您必须使用：|1714655|docker+build+-t+imagename+-f+Dockerfile2+.|1714656|那么复制就像预期的那样起作用了。|1714657|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Seems that the commands:

<pre><code>docker build -t imagename .
</code></pre>

and: 

<pre><code>docker build -t imagename - &lt; Dockerfile2
</code></pre>

are not executed the same way. If you want to build 2 docker images from within one folder with Dockerfile and Dockerfile2, the COPY command cannot be used in the second example using stdin (&lt; Dockerfile2).
Instead you have to use:

<pre><code>docker build -t imagename -f Dockerfile2 .
</code></pre>

Then COPY does work as expected.

blocks|key|551261|text|运行docker+build+.+-f+docker/development/Dockerfile有效，允许您从应用程序根目录以外的指定目录运行停靠文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|551262|使用-f或--file指定Dockerfile的名称和位置。|551263|这种情况发生在我试图从另一个目录运行docker文件时。|551264|我有COPY+failed:+stat+/var/lib/docker/tmp/docker-builder929708051/XXXX:+no+such+file+or+directory，并通过指定docker文件来解决这个问题。|551265|是docker+build+docker/development/Dockerfile给我造成了这个问题。|551266|一开始我觉得很奇怪，因为当我在应用程序根目录中使用Dockerfile时，它工作得很好。如果您想要更好地管理您的环境停靠文件，这将有所帮助。|551267|entityMap^0|2|1B|0|2|2|5|6|D|A|0|0|2|2L|0|1|16|0|P|A|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|11|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|18|8|@$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|P|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|Q|$]]

Running <code>docker build . -f docker/development/Dockerfile</code> worked, which allows you to run your docker file from a specified directory other than the root of your application.
Use <code>-f</code> or <code>--file</code> to specify the name and location of the <code>Dockerfile</code>.
This happened to me when trying to run the docker file from a different directory.
I had the <code>COPY failed: stat /var/lib/docker/tmp/docker-builder929708051/XXXX: no such file or directory</code> and managed to resolve this by specifying the docker file.
It was <code>docker build docker/development/Dockerfile</code> that caused this issue for me.
I found it strange at first because when i had the <code>Dockerfile</code> in the apps root directory it worked fine. This will help if you want to manage your environment docker files a little better.

blocks|key|1162930|text|我刚经历过这个问题，这里的建议都解决不了我的问题。结果发现，文件中出现了错误的行尾，必须将它们更改为适当的行尾。(在这个例子中，从CRLF到LF，所以Ubuntu14.04会识别脚本，我一直在windows上编辑它。)|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1162931|我使用VSCode更改了行尾，大多数代码编辑器应该可以选择行尾。|1162932|希望这能帮上忙。|1162933|entityMap^0|U|B|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|P|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|K|$]]

I just experienced this problem and none of the suggestions here solved my problem.
Turns out I had the wrong line endings in my file, and had to change them to the appropriate line endings. (In this case from CRLF to LF, so Ubuntu 14.04 would recognize the script, which I had been editing on windows.)

I changed the line endings using VSCode, and most code editors should have the option of choosing line endings.

Hope this helps someone.

blocks|key|551579|text|在PS上执行docker+build+-+<+Dockerfile或Get-Content+.\Dockerfile+%7C+Docker+build+-可能无法获得上下文。我建议你用|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|551580|Docker+build+-f+.\Path\Dockerfile+.+|code-block|syntax|javascript|551581|entityMap^0|6|R|Y|15|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

Doing a <code>docker build - &lt; Dockerfile</code> or <code>Get-Content .\Dockerfile | Docker build -</code>on PS might not be getting the context. I would recommend you use
<pre><code>Docker build -f .\Path\Dockerfile . 
</code></pre>

blocks|key|1163018|text|以下是解决方案和最佳做法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1163019|您需要创建一个资源文件夹，在该文件夹中可以保存要复制的所有文件。|1163020|├──+Dockerfile
└──+resources
│+++++├──+file1.txt
│+++++├──+file2.js|code-block|syntax|javascript|1163021|应以下列方式指定用于复制文件的命令：|1163022|COPY+resources+/root/folder/|1163023|哪里|1163024|*resources+-您在Dockerfile所在的同一文件夹中创建的本地文件夹|offset|length|style|BOLD|1163025|*/root/folder/+-容器处的文件夹|1163026|entityMap^0|0|0|0|0|0|0|1|9|0|1|D|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|14|8|@$Q|15|R|16|S|T]]|9|@]|A|$]]|$1|U|3|V|5|6|7|17|8|@$Q|18|R|19|S|T]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|X|$]]

Here is the solution and the best practice:
You need to create a resources folder where you can keep all your files you want to copy.
<pre><code>├── Dockerfile
└── resources
│ ├── file1.txt
│ ├── file2.js
</code></pre>
The command for copying files should be specified this way:
<pre><code>COPY resources /root/folder/
</code></pre>
where
*resources - your local folder which you created in the same folder where Dockerfile is
*/root/folder/ - folder at your container

blocks|key|1714736|text|我觉得有点愚蠢，但我的问题是，我正在运行Dockerfile，而我的Dockerfile位于./部署子目录中。我的ADD引用需要相对于项目的根，而不是Dockerfile。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1714737|更改:添加./file.tar.gz+/etc/文件夹/+to:+ADD+./部署/file.tar.gz/etc/文件夹/|1714738|不管怎样，我想我会发邮件以防有人碰到同样的问题。|1714739|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I feel a little stupid, but my issue was that I was running docker-compose, and my Dockerfile was in a ./deploy subdirectory. My ADD reference needed to be relative to the root of the project, not the Dockerfile.

Changed:
ADD ./file.tar.gz /etc/folder/
to:
ADD ./deploy/file.tar.gz /etc/folder/

Anyhow, thought I'd post in case someone ran into the same issue.

blocks|key|1162910|text|以前对副本的调用可能正在更改目录。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1162911|COPY+./server/package.json+./server++++++#+this+passes,+but+the+dest+./server+is+considered+a+file

COPY+./server/dist+./server/dist+++++++++#+error,+./server/dist+is+not+a+directory|code-block|syntax|javascript|1162912|在第一个调用中添加一个尾斜杠|1162913|COPY+./server/package.json+./server/|1162914|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Previous calls on COPY may be changing the directory. 

<pre><code>COPY ./server/package.json ./server # this passes, but the dest ./server is considered a file

COPY ./server/dist ./server/dist # error, ./server/dist is not a directory
</code></pre>

Add a trailing slash to the first call

<pre><code>COPY ./server/package.json ./server/
</code></pre>

blocks|key|1715084|text|我知道这很古老，但我要指出的是。如果您认为一切都是应该的，请检查您的.gitignore文件:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1715085|您可能在本地拥有该文件夹，但如果该文件夹位于git中，则它不在服务器上，这意味着Docker无法找到该文件夹，因为它不存在。|1715086|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I know this is old, but something to point out. If you think everything is as its supposed to, check your .gitignore file :) 

You might have the folder locally, but if the folder is in your git ignore then its not on the server, which means Docker cannot find that folder as it does not exist.

blocks|key|1715147|text|类似的，感谢三叉神经炎的回答，之后|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1715148|gcloud+builds+submit+--config+cloudbuild.yaml+.+|code-block|syntax|javascript|1715149|它显示了|1715150|Check+the+gcloud+log+[/home/USER/.config/gcloud/logs/2020.05.24/21.12.04.NUMBERS.log]+to+see+which+files+and+the+contents+of+the
default+gcloudignore+file+used+(see+`$+gcloud+topic+gcloudignore`+to+learn
more).|1715151|检查日志，它说码头将使用.gitignore|style|CODE|1715152|DATE+Using+default+gcloudignore+file:
#+This+file+specifies+files+that+are+*not*+uploaded+to+Google+Cloud+Platform
#+using+gcloud.+It+follows+the+same+syntax+as+.gitignore,+with+the+addition+of
#+"#!include"+directives+(which+insert+the+entries+of+the+given+.gitignore-style
#+file+at+that+point).
#+...

.gitignore|1715153|因此，我修复了我的.gitignore+(我使用它作为白名单)并复制文件。|1715154|我补充了答案，因为我没有足够的声誉来评论。|1715155|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/users/2768651/tslegaitis^0|6|5|0|0|0|0|0|C|A|0|0|9|A|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|F|7|18|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|19|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|1A|8|@]|9|@]|C|$G|H]]|$1|M|3|N|5|6|7|1B|8|@$A|1C|B|1D|O|P]]|9|@]|C|$]]|$1|Q|3|R|5|F|7|1E|8|@]|9|@]|C|$G|H]]|$1|S|3|T|5|6|7|1F|8|@$A|1G|B|1H|O|P]]|9|@]|C|$]]|$1|U|3|V|5|6|7|1I|8|@]|9|@]|C|$]]|$1|W|3|-4|5|6|7|1J|8|@]|9|@]|C|$]]]|X|$Y|$5|Z|10|11|C|$12|13]]]]

Similar and thanks to <a href="https://stackoverflow.com/users/2768651/tslegaitis">tslegaitis</a>'s answer, after 

<pre><code>gcloud builds submit --config cloudbuild.yaml . 
</code></pre>

it shows

<pre><code>Check the gcloud log [/home/USER/.config/gcloud/logs/2020.05.24/21.12.04.NUMBERS.log] to see which files and the contents of the
default gcloudignore file used (see `$ gcloud topic gcloudignore` to learn
more).
</code></pre>

Checking that log, it says that docker will use <code>.gitignore</code>:

<pre><code>DATE Using default gcloudignore file:
# This file specifies files that are *not* uploaded to Google Cloud Platform
# using gcloud. It follows the same syntax as .gitignore, with the addition of
# "#!include" directives (which insert the entries of the given .gitignore-style
# file at that point).
# ...

.gitignore
</code></pre>

So I fixed my <code>.gitignore</code> (I use it as whitelist instead) and docker copied the file.

[I added the answer because I have not enough reputation to comment]

blocks|key|551570|text|尽管我的源目录位于正确的构建上下文中，但我还是遇到了这个问题。找到原因是，我的源目录是指向构建上下文之外的位置的符号链接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|551571|例如，我的Dockerfile包含以下内容：|551572|COPY+dir1+/tmp|code-block|syntax|javascript|551573|如果dir1是一个符号链接，那么在我的示例中，COPY命令就无法工作。|offset|length|style|CODE|551574|entityMap^0|0|0|0|2|4|N|4|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@$K|U|L|V|M|N]|$K|W|L|X|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

I had this problem even though my source directory was in the correct build context. Found the reason was that my source directory was a symbolic link to a location outside the build context.
For example my Dockerfile contains the following:
<pre><code>COPY dir1 /tmp
</code></pre>
If <code>dir1</code> is a symbolic link the <code>COPY</code> command is not working in my case.

blocks|key|551631|text|问题在于：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|551632|如果使用STDIN+(停靠器生成-<+somefile)进行构建，则没有生成上下文，因此无法使用复制。|blockquote|offset|length|style|BOLD|551633|有关更多信息：https://docs.docker.com/engine/reference/builder/#copy|551634|就这样建造码头吧：|551635|docker+build+-t+name-of-your-tag+.|code-block|syntax|javascript|551636|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/engine/reference/builder/#copy^0|0|0|1F|0|7|1I|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|10|8|@$E|11|F|12|G|H]]|9|@]|A|$]]|$1|I|3|J|5|6|7|13|8|@]|9|@$E|14|F|15|1|16]]|A|$]]|$1|K|3|L|5|6|7|17|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|18|8|@]|9|@]|A|$P|Q]]|$1|R|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]]]

The problem is here:
<blockquote>
If you build using STDIN (docker build - &lt; somefile), there is no
build context, so COPY can’t be used.
</blockquote>
For more information: <a href="https://docs.docker.com/engine/reference/builder/#copy" rel="nofollow noreferrer">https://docs.docker.com/engine/reference/builder/#copy</a>
Just build docker in this way:
<pre><code>docker build -t name-of-your-tag .
</code></pre>

blocks|key|1162810|text|对于后续的错误，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1162811|COPY+failed:+stat+/<**path**>+:no+such+file+or+directory|code-block|syntax|javascript|1162812|我通过重新启动码头服务来解决这个问题。|1162813|sudo+service+docker+restart|1162814|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

For following error,

<pre><code>COPY failed: stat /&lt;**path**&gt; :no such file or directory
</code></pre>

I got it around by restarting docker service.

<pre><code>sudo service docker restart
</code></pre>

blocks|key|1714804|text|Docker+put_archive文件未找到错误。我正在使用Python进行对接。Docker版本1.12.5，构建7392c3b|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1714805|docker.errors.NotFound:+404+Client+Error:+Not+Found+("lstat+/var/lib/docker/aufs/mnt/39d58e00519ba4171815ee4444f3c43d2c6a7e285102747398f6788e39ee0e87/var/lib/neo4j/certificates:+no+such+file+or+directory")|code-block|syntax|javascript|1714806|我无法将文件复制到已创建的坞容器中。|1714807|con+=+cli.create_container(...)
cli.put_archive(...)
cli.start(con['Id'])|1714808|如果更改操作顺序，则没有错误，文件被复制到我想要的位置。所以我知道我的代码起作用了，并且做了我想做的事情。但是，在容器启动之前将配置文件复制到容器中非常重要。在开始后处理文件时，裁剪容器将从默认配置开始，而不是在容器启动之前复制到需要复制到位置的自定义配置。Docker声称这个问题已经结束，但它仍然影响我的应用程序。|1714809|这是可行的；相同的代码，不同的执行顺序。|1714810|con+=+cli.create_container(...)
cli.start(con['Id'])
cli.put_archive(...)|1714811|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|Y|8|@]|9|@]|A|$E|F]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

File not found error with Docker put_archive. I am using the Python API for docker. 
Docker version 1.12.5, build 7392c3b

<pre><code>docker.errors.NotFound: 404 Client Error: Not Found ("lstat /var/lib/docker/aufs/mnt/39d58e00519ba4171815ee4444f3c43d2c6a7e285102747398f6788e39ee0e87/var/lib/neo4j/certificates: no such file or directory")
</code></pre>

I am unable to copy files to a created docker container.

<pre><code>con = cli.create_container(...)
cli.put_archive(...)
cli.start(con['Id'])
</code></pre>

If I change the order of operation there is no error and the files are copied exactly to were I want them. So I know my code is working and doing what I want it to do. But its important to copy configuration files to a container before it is started. Coping the files after the start cuases the container to start with a default configuration and not the custom configuration which needs to be copied into place before the container is started. Docker claims that this issue is closed but it is still affecting my application.

This works; Same code different execution order.

<pre><code>con = cli.create_container(...)
cli.start(con['Id'])
cli.put_archive(...)
</code></pre>

blocks|key|1714833|text|如果你确信你做了正确的事情，但码头仍然抱怨，看看这个问题：https://github.com/moby/moby/issues/27134。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1714834|我被这个烧掉了，看来重新启动码头引擎service+docker+restart就能解决这个问题。|style|CODE|1714835|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/moby/moby/issues/27134^0|T|15|0|0|I|M|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@$A|U|B|V|F|G]]|9|@]|C|$]]|$1|H|3|-4|5|6|7|W|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

if you are sure that you did the right thing, but docker still complains, take a look at this issue: <a href="https://github.com/moby/moby/issues/27134" rel="nofollow noreferrer">https://github.com/moby/moby/issues/27134</a>. 
I got burnt by this, and it seems like restarting docker engine <code>service docker restart</code> will just fix this problem.

blocks|key|551299|text|我正在搜索该文件的修复程序，而我添加或复制的文件夹不在build文件夹中，上面的多个目录或来自/|type|unstyled|depth|inlineStyleRanges|entityRanges|data|551300|将文件夹从生成文件夹外部移动到build文件夹中，解决了我的问题。|551301|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I was searching for a fix on this and the folder i was ADD or COPY'ing was not in the build folder, multiple directories above or referenced from /

Moving the folder from outside the build folder into the build folder fixed my issue.

blocks|key|551321|text|不使用stdin并保持上下文的方法之一是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|551322|1)在您的Dockerfile中，应该添加|551323|ADD+/your_dir_to_copy+/location_in_container|code-block|syntax|javascript|551324|2)之后，您应该选择/your_dir_to_copy+dir的父级|551325|2)然后运行以下命令|551326|sudo+docker+build+.+-t+(image/name)+-f+path_of_your_dockerfile/Dockerfile|551327|3)在创建容器之后|551328|docker+run+-ti+--rm+cordova+bash|551329|4)在将目录复制到容器中之后|551330|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|11|8|@]|9|@]|A|$G|H]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|13|8|@]|9|@]|A|$G|H]]|$1|S|3|T|5|6|7|14|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

one of the way to don't use stdin and keep the context is:

1) in your Dockerfile, you should add

<pre><code>ADD /your_dir_to_copy /location_in_container
</code></pre>

2) after, you should go on the parent of /your_dir_to_copy dir

2) then run this command

<pre><code>sudo docker build . -t (image/name) -f path_of_your_dockerfile/Dockerfile
</code></pre>

3) after you create your container

<pre><code>docker run -ti --rm cordova bash
</code></pre>

4) After you will get your directory copied in your container

blocks|key|551401|text|我碰到这个了。复制某些目录不起作用。复制文件。结果发现，这是因为.gitignore+(不仅仅是.dockerignore)中包含的文件也被忽略了。请参阅：https://github.com/zeit/now/issues/790|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|551402|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/zeit/now/issues/790^0|26|12|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I ran into this. Copying some directories didn't work. Copying files did. It turned out to be because files contained in .gitignore (not just .dockerignore) are also ignored. See: <a href="https://github.com/zeit/now/issues/790" rel="nofollow noreferrer">https://github.com/zeit/now/issues/790</a>

blocks|key|1163273|text|我自己也遇到过，这里的解决方案都没有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1163274|最后，原因是我运行的容器错误。我正在构建容器/名称，并运行容器/名称:1.0，这是以前构建的。|offset|length|style|BOLD|1163275|换句话说，检查您是否构建并运行了完全相同的容器。|1163276|entityMap^0|0|7|5|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Ran into this myself, and none of the solutions here worked.
Finally, the reason was that I was running wrong container. I was building container/name and was running container/name:1.0, which was built previously.
In other words, check that you build &amp; run exactly the same container.

blocks|key|1715032|text|最近发生过几次这样的事情。作为一个.Net开发工具，我使用VisualStudio将构建名从SomeThing更改为Something作为DLL名称，但这不会更改保留SomeThing.csproj的.csproj文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1715033|Dockerfile使用linux区分大小写的文件名，因此新生成的Dockerfile试图复制无法找到的Something.csproj。因此，手动重命名该文件(使其小写)使其全部正常工作。|1715034|但是.这里有个警告。我的Windows笔记本电脑上的文件名更改不会被Git获取，因此回购程序的源代码仍然是SomeThing.csproj在回购程序中，并且在CI/CD过程中，Docker构建失败的原因是相同的.|1715035|我不得不直接更改文件名，作为对repo....nasty小解决方案的提交，但却让我开始工作。|1715036|tl;dr如果在Windows+O/S上检查文件名是否对大小写敏感，并注意本地文件重命名不会随着Git的更改而被拾取，所以如果使用CI/CD，请确保您的repo也被修改|1715037|entityMap^0|1A|9|1M|9|2B|G|0|1G|G|0|1H|G|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|12|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|13|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|O|$]]

So this has happened a couple of times just recently. As a .Net dev, using VisualStudio I changed my build name from <code>SomeThing</code> to <code>Something</code> as the DLL name but this does not change the .csproj file which stays <code>SomeThing.csproj</code>

The Dockerfile uses linux case-sensitive filenames, so the newly autogenerated Dockerfile was trying to copy <code>Something.csproj</code> which it couldn't find. So manually renaming that file (making it lowercase) got it all working

But...here's a cautionary warning. This filename change on my Windows laptop does not get picked up by Git so the repo source was still <code>SomeThing.csproj</code> on the repo and during the CI/CD process, the Docker build failed for the same reasons...

I had to change the filename directly as a commit on the repo....nasty little workaround but got me going 

tl;dr If on Windows O/S check for filename case sensitivity and be aware local file renames do not get picked up as Git change so make sure your repo is also modified if using CI/CD

I have a Dockerfile set up in my root (~) folder. The first three lines of my file look like this:

<pre><code>COPY file1 /root/folder/
COPY file2 /root/folder/
COPY file3 /root/folder/
</code></pre>

but it returns the following error for each line:

<blockquote>
 No such file or directory
</blockquote>

The files are in the same directory as my Dockerfile and I am running the command <code>docker build - &lt; Dockerfile</code> in the same directory in terminal as well.

What am I doing wrong here exactly?

COPYing a file in a Dockerfile, no such file or directory?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我在根(~)文件夹中设置了一个Dockerfile。我文件的前三行如下所示：COPY file1 /root/folder/COPY file2 /root/folder/COPY file3 /root/folder/但是，它为每一行返回以下错误：文件或目录不存在这些文件与我的Dockerfile位于同一个目录中，我也在终端的同一个目录中运行命令docker build - < Dockerfi

问COPYing文件中的一个文件，没有这样的文件或目录？
EN

回答 22

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问COPYing文件中的一个文件，没有这样的文件或目录？EN

回答 22

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问COPYing文件中的一个文件，没有这样的文件或目录？
EN