blocks|key|1700699|text|正如docker-compose+run+(2015)中提到的那样|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1700700|1700701|+运行传递的命令会覆盖服务配置中定义的命令。|blockquote|BOLD|1700702|1700703|例如，如果web服务配置是使用bash启动的，则docker-compose+run+web+python+app.py将使用python+app.py覆盖它。|1700704|第二个区别是docker-compose+run命令不会创建服务配置中指定的任何端口。|1700705|这可防止端口与已打开的端口发生冲突。如果您确实希望创建服务的端口并将其映射到主机，请指定--service-ports标志：|1700706|1700707|$+docker-compose+run+--service-ports+web+python+manage.py+shell|code-block|syntax|javascript|1700708|因此，除非您有这些特定的需求(覆盖命令或在不同的端口上只运行一个容器)，否则docker-compose+up+(即使对于一个容器)就足够了。|1700709|1700710|您能否帮助解释为什么或何时不希望创建端口？这就是它们可能与已经开放的端口冲突的原因或时间|1700711|1700712|1700713|很简单，因为docker-compose+run是为您的服务运行一次性命令的。|1700714|这意味着，如果您已经创建了一个docker-compose+up，那么您的所有容器都已经在docker-compose.yml指定的端口上运行了。|1700715|在此阶段执行docker-compose+run+(执行一次性命令)，如果它涉及同一端口，将立即失败。因此，默认情况下不创建这些端口。|1700716|1700717|另一个用例(在Compose+environment+variables+reference中)：|1700718|1700719|要查看服务可用的环境变量，请运行docker-compose+run+SERVICE+env。|1700720|1700721|1700722|1700723|这些命令的最新(2019%2B)版本位于docker/docker.github.io上|1700724|1700725|docker+compose+run|unordered-list-item|1700726|docker+compose+up|1700727|1700728|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/docker/compose/blob/17682c58db8986f1d1492559d72b3960b86f5f05/docs/reference/run.md|1|https://github.com/docker/compose/blob/d577cd6877f9f8480f13cdbba3f2cf17e9c3d5eb/docs/env.md|2|https://github.com/docker/docker.github.io|3|https://github.com/docker/docker.github.io/blob/master/compose/reference/run.md|4|https://github.com/docker/docker.github.io/blob/master/compose/reference/up.md^0|2|I|2|I|0|0|0|1|E|0|0|F|4|O|10|1R|D|0|6|I|Q|8|0|0|0|0|12|H|0|0|0|0|0|6|I|0|F|H|19|I|0|6|I|0|0|7|13|1|0|0|G|U|0|0|0|0|I|N|I|N|2|0|0|0|I|0|I|3|0|0|H|0|H|4|0|0^^$0|@$1|2|3|4|5|6|7|28|8|@$9|29|A|2A|B|C]]|D|@$9|2B|A|2C|1|2D]]|E|$]]|$1|F|3|-4|5|6|7|2E|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|2F|8|@$9|2G|A|2H|B|J]]|D|@]|E|$]]|$1|K|3|-4|5|6|7|2I|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|2J|8|@$9|2K|A|2L|B|C]|$9|2M|A|2N|B|C]|$9|2O|A|2P|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|2Q|8|@$9|2R|A|2S|B|C]|$9|2T|A|2U|B|J]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|2V|8|@]|D|@]|E|$]]|$1|R|3|-4|5|6|7|2W|8|@]|D|@]|E|$]]|$1|S|3|T|5|U|7|2X|8|@]|D|@]|E|$V|W]]|$1|X|3|Y|5|6|7|2Y|8|@$9|2Z|A|30|B|C]]|D|@]|E|$]]|$1|Z|3|-4|5|6|7|31|8|@]|D|@]|E|$]]|$1|10|3|11|5|I|7|32|8|@]|D|@]|E|$]]|$1|12|3|-4|5|6|7|33|8|@]|D|@]|E|$]]|$1|13|3|-4|5|6|7|34|8|@]|D|@]|E|$]]|$1|14|3|15|5|6|7|35|8|@$9|36|A|37|B|C]]|D|@]|E|$]]|$1|16|3|17|5|6|7|38|8|@$9|39|A|3A|B|C]|$9|3B|A|3C|B|C]]|D|@]|E|$]]|$1|18|3|19|5|6|7|3D|8|@$9|3E|A|3F|B|C]]|D|@]|E|$]]|$1|1A|3|-4|5|6|7|3G|8|@]|D|@]|E|$]]|$1|1B|3|1C|5|6|7|3H|8|@]|D|@$9|3I|A|3J|1|3K]]|E|$]]|$1|1D|3|-4|5|6|7|3L|8|@]|D|@]|E|$]]|$1|1E|3|1F|5|I|7|3M|8|@$9|3N|A|3O|B|C]]|D|@]|E|$]]|$1|1G|3|-4|5|6|7|3P|8|@]|D|@]|E|$]]|$1|1H|3|-4|5|6|7|3Q|8|@]|D|@]|E|$]]|$1|1I|3|-4|5|6|7|3R|8|@]|D|@]|E|$]]|$1|1J|3|1K|5|6|7|3S|8|@$9|3T|A|3U|B|C]]|D|@$9|3V|A|3W|1|3X]]|E|$]]|$1|1L|3|-4|5|6|7|3Y|8|@]|D|@]|E|$]]|$1|1M|3|1N|5|1O|7|3Z|8|@$9|40|A|41|B|C]]|D|@$9|42|A|43|1|44]]|E|$]]|$1|1P|3|1Q|5|1O|7|45|8|@$9|46|A|47|B|C]]|D|@$9|48|A|49|1|4A]]|E|$]]|$1|1R|3|-4|5|6|7|4B|8|@]|D|@]|E|$]]|$1|1S|3|-4|5|6|7|4C|8|@]|D|@]|E|$]]]|1T|$1U|$5|1V|1W|1X|E|$1Y|1Z]]|20|$5|1V|1W|1X|E|$1Y|21]]|22|$5|1V|1W|1X|E|$1Y|23]]|24|$5|1V|1W|1X|E|$1Y|25]]|26|$5|1V|1W|1X|E|$1Y|27]]]]

As mentioned in <a href="https://github.com/docker/compose/blob/17682c58db8986f1d1492559d72b3960b86f5f05/docs/reference/run.md" rel="noreferrer"><code>docker-compose run</code></a> (2015)

<blockquote>
 The command passed by run overrides the command defined in the service configuration. 
 For example, if the web service configuration is started with <code>bash</code>, then <code>docker-compose run web python app.py</code> overrides it with <code>python app.py</code>.
 
 The second difference is the <code>docker-compose run</code> command does not create any of the ports specified in the service configuration. 
 This prevents the port collisions with already open ports. If you do want the service's ports created and mapped to the host, specify the --service-ports flag:
</blockquote>

<pre><code>$ docker-compose run --service-ports web python manage.py shell
</code></pre>

So unless you have those specific needs (overriding a command or running only one container on different ports), <code>docker-compose up</code> (even for one container) is enough.

<blockquote>
 Can you help explain why or when you would not want the ports to be created? That is why or when they might conflict with already open ports
</blockquote>

Simply because <code>docker-compose run</code> is made to run one-off commands for your services. 
That means that, if you already did a <code>docker-compose up</code>, all your containers are already running on their specified ports from <code>docker-compose.yml</code>. 
Doing a <code>docker-compose run</code> at this stage (to execute a one-off command), if it was respecting the same port, would fail immediately. Hence the default non-creation of those ports.

<hr>

Another use case (in <a href="https://github.com/docker/compose/blob/d577cd6877f9f8480f13cdbba3f2cf17e9c3d5eb/docs/env.md" rel="noreferrer">Compose environment variables reference</a>):

<blockquote>
 To see what environment variables are available to a service, run <code>docker-compose run SERVICE env</code>.
</blockquote>

<hr>

Most recent (2019+) version of those commands are on <a href="https://github.com/docker/docker.github.io" rel="noreferrer"><code>docker/docker.github.io</code></a>:

<ul>
<li><a href="https://github.com/docker/docker.github.io/blob/master/compose/reference/run.md" rel="noreferrer"><code>docker compose run</code></a></li>
<li><a href="https://github.com/docker/docker.github.io/blob/master/compose/reference/up.md" rel="noreferrer"><code>docker compose up</code></a></li>
</ul>

blocks|key|1700730|text|我想指出的是，如果您在pdb调试器中使用Python：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1700731|import+pdb;+pdb.set_trace()|code-block|syntax|javascript|1700732|如果您使用以下命令执行脚本，则不会将其放到shell中：|1700733|docker-compose+up|1700734|但是，如果你使用run，它会像预期的那样下拉到调试器：|1700735|docker-compose+run|1700736|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I'd like to point out that if you're using Python with the pdb debugger:

<pre><code>import pdb; pdb.set_trace()
</code></pre>

It will not drop to the shell if you execute your script using:

<pre><code>docker-compose up
</code></pre>

However if you use run, it will drop down to the debugger as expected:

<pre><code>docker-compose run
</code></pre>

blocks|key|5992250|text|docker+docs给出了答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5992251|通常情况下，您需要docker-compose+up。使用up启动或重新启动docker-compose.yml中定义的所有服务。在默认的“附加”模式下，您可以看到来自所有容器的所有日志。在“分离”模式(-d)下，Compose在启动容器后退出，但容器继续在后台运行。|style|CODE|5992252|docker-compose+run命令用于运行“一次性”或“临时”任务。它需要您想要运行的服务名称，并且只为运行的服务所依赖的服务启动容器。使用run运行测试或执行管理任务，例如删除数据卷容器或向数据卷容器添加数据。run命令的作用类似于docker+run+-ti，因为它打开了一个指向容器的交互式终端，并返回一个与容器中进程的退出状态相匹配的退出状态。|5992253|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/compose/faq/#whats-the-difference-between-up-run-and-start^0|0|B|0|0|9|H|T|2|12|I|2U|2|0|0|I|21|3|31|3|3C|E|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@$A|W|B|X|F|G]|$A|Y|B|Z|F|G]|$A|10|B|11|F|G]|$A|12|B|13|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|14|8|@$A|15|B|16|F|G]|$A|17|B|18|F|G]|$A|19|B|1A|F|G]|$A|1B|B|1C|F|G]]|9|@]|C|$]]|$1|J|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

There is an answer from <a href="https://docs.docker.com/compose/faq/#whats-the-difference-between-up-run-and-start" rel="noreferrer">docker docs</a>.

<blockquote>
 Typically, you want <code>docker-compose up</code>. Use <code>up</code> to start or restart all
 the services defined in a <code>docker-compose.yml</code>. In the default
 “attached” mode, you see all the logs from all the containers. In
 “detached” mode (<code>-d</code>), Compose exits after starting the containers, but
 the containers continue to run in the background.
 
 The <code>docker-compose run</code> command is for running “one-off” or “adhoc”
 tasks. It requires the service name you want to run and only starts
 containers for services that the running service depends on. Use <code>run</code>
 to run tests or perform an administrative task such as removing or
 adding data to a data volume container. The <code>run</code> command acts like
 <code>docker run -ti</code> in that it opens an interactive terminal to the
 container and returns an exit status matching the exit status of the
 process in the container.
</blockquote>

Is there a reason to use <code>run</code> to start up a <code>docker-compose.yml</code> file or should you just use <code>up</code>?

I understand that <code>run</code> can start up a specific container, but I am referring to the case where you use it without specifying a container so that it starts up all of your yml containers.

Should I use docker-compose up or run?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

有没有理由使用run来启动docker-compose.yml文件，或者应该只使用up我知道run可以启动一个特定的容器，但我指的是在不指定容器的情况下使用它，以便它启动所有的yml容器。

问我应该使用docker-compose up还是run？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我应该使用docker-compose up还是run？EN