<p>你在<a href="https://github.com/docker/compose/issues/1616#issuecomment-116879169" rel="nofollow noreferrer">issue 1616</a>中也有同样的问题</p>
<blockquote>
<p>the issue appears to primarily be a consequence of the ADD/WORKDIR in the Dockerfile:</p>
</blockquote>
<pre><code>ADD . /code
WORKDIR /code
</code></pre>
<blockquote>
<p>Conflicting with the volume mapping in the docker-compose.yml</p>
</blockquote>
^{pr2}$
<blockquote>
<p>I may have misread the instructions but had both.</p>
</blockquote>
<p>原因:</p>
<blockquote>
<p>When running an app on a remote host, you'll need to remove any <code>volumes</code> entries that mount anything in from a local directory.</p>
<p>The reason we promote both adding your code to the image and mounting it as a volume is so that doing a <code>docker-compose build</code> gets you an image that's ready to deploy to a remote server, but whose code can still be mounted when developing locally so it can be live-reloaded.</p>
<p>If you want to use Compose to both develop an app locally and deploy it to the cloud, the best practice is to have a file for each - <code>docker-compose.yml</code> for local development and something else (e.g. <code>remote.yml</code>) for remote deployment - and use the <code>-f</code> flag to pass the alternate file in when deploying.</p>
<p>You can use the <a href="https://docs.docker.com/compose/extends/" rel="nofollow noreferrer"><code>extends</code> option</a> to reduce duplication between both files.</p>
</blockquote>
<hr/>
<p>在Windows上,请注意路径及其共享状态:请参见<a href="https://github.com/docker/compose/issues/3157#issuecomment-198328642" rel="nofollow noreferrer">issue 3157</a>。在</p>