blocks|key|4425678|text|您需要在docker-compose.yml中包含以下行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4425679|version:+"3"
services:
++app:
++++image:+app:1.2.3
++++stdin_open:+true+#+docker+run+-i
++++tty:+true++++++++#+docker+run+-t|code-block|syntax|javascript|4425680|第一个对应于docker+run中的-i，第二个对应于-t。|offset|length|style|CODE|4425681|entityMap^0|0|0|6|A|I|2|R|2|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]|$I|V|J|W|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|N|$]]

You need to include the following lines in your docker-compose.yml:

<pre class="lang-yaml prettyprint-override"><code>version: "3"
services:
 app:
 image: app:1.2.3
 stdin_open: true # docker run -i
 tty: true # docker run -t

</code></pre>

The first corresponds to <code>-i</code> in <code>docker run</code> and the second to <code>-t</code>.

blocks|key|4425707|text|使用docker-compose获得交互式shell的规范方法是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4425708|docker-compose+run+--rm+myapp|code-block|syntax|javascript|4425709|你可以设置stdin_open:+true,+tty:+true，但是这实际上不会给你一个合适的up外壳，因为日志是从所有容器中流出的。|offset|length|style|CODE|4425710|您还可以使用|4425711|docker+exec+-ti+<container+name>+/bin/bash|4425712|获取正在运行的容器上的shell。|4425713|entityMap^0|0|0|5|R|1C|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@$I|X|J|Y|K|L]|$I|Z|J|10|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|12|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

The canonical way to get an interactive shell with docker-compose is to use:
<pre><code>docker-compose run --rm myapp
</code></pre>
You can set <code>stdin_open: true, tty: true</code>, however that won't actually give you a proper shell with <code>up</code>, because logs are being streamed from all the containers.
You can also use
<pre><code>docker exec -ti &lt;container name&gt; /bin/bash
</code></pre>
to get a shell on a running container.

blocks|key|4425775|text|在具有以下docker-compose.yml的官方入门示例(https://docs.docker.com/compose/gettingstarted/)中|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4425776|version:+'3'
services:
++web:
++++build:+.
++++ports:
+++++-+"5000:5000"
++redis:
++++image:+"redis:alpine"|code-block|syntax|javascript|4425777|在开始使用docker-compose+up之后，您可以使用以下命令轻松地外壳到redis容器或web容器中：|4425778|docker-compose+exec+redis+sh
docker-compose+exec+web+sh+|4425779|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/compose/gettingstarted/^0|5|I|V|1B|0|0|0|5|H|14|5|1C|3|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|F|3|G|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|13|8|@$9|14|A|15|B|C]|$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|1A|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

In the official getting started example (<a href="https://docs.docker.com/compose/gettingstarted/" rel="noreferrer">https://docs.docker.com/compose/gettingstarted/</a>) with the following <code>docker-compose.yml</code>:

<pre><code>version: '3'
services:
 web:
 build: .
 ports:
 - "5000:5000"
 redis:
 image: "redis:alpine"
</code></pre>

After you start this with <code>docker-compose up</code>, you can easily shell into either your <code>redis</code> container or your <code>web</code> container with:

<pre><code>docker-compose exec redis sh
docker-compose exec web sh 
</code></pre>

blocks|key|4425824|text|docker-compose+run+myapp+sh应该做这笔交易。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4425825|up/run有一些混淆，但docker-compose+run文档有很好的解释：https://docs.docker.com/compose/reference/run|4425826|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/compose/reference/run^0|0|R|0|0|2|3|3|D|I|14|19|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|H|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

<code>docker-compose run myapp sh</code> should do the deal.

There is some confusion with <code>up</code>/<code>run</code>, but <code>docker-compose run</code> docs have great explanation: <a href="https://docs.docker.com/compose/reference/run" rel="noreferrer">https://docs.docker.com/compose/reference/run</a>

blocks|key|4425838|text|如果来自未来的任何人也在这里徘徊：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4425839|docker-compose+exec+container_name+sh|code-block|syntax|javascript|4425840|或|4425841|docker-compose+exec+container_name+bash|4425842|或者，您可以像这样运行单行|4425843|docker-compose+exec+container_name+php+-v|4425844|这是在您已经启动并运行了容器之后|4425845|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|$]]

If anyone from the future also wanders up here:

<pre><code>docker-compose exec container_name sh
</code></pre>

or

<pre><code>docker-compose exec container_name bash
</code></pre>

or you can run single lines like

<pre><code>docker-compose exec container_name php -v
</code></pre>

That is after you already have your containers up and running

blocks|key|4425760|text|使用docker-compose，我发现最简单的方法是做一个docker+ps+-a+(在用docker-compose+up启动我的容器之后)，并获得我想要在其中拥有一个交互式外壳的容器的ID+(让我们称之为xyz123)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4425761|然后执行docker+exec+-ti+xyz123+/bin/bash就很简单了|4425762|瞧，这是一个交互式的shell。|4425763|entityMap^0|U|C|1A|H|0|4|W|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|K|$]]

Using docker-compose, I found the easiest way to do this is to do a <code>docker ps -a</code> (after starting my containers with <code>docker-compose up</code>) and get the ID of the container I want to have an interactive shell in (let's call it xyz123). 

Then it's a simple matter to execute
<code>docker exec -ti xyz123 /bin/bash</code>

and voila, an interactive shell.

blocks|key|4425932|text|如果yml名为docker-compose.yml，则可以使用简单的$+docker-compose+up启动它。终端的相应附件可以是简单的(考虑到yml已经指定了名为myservice的服务)：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4425933|$+docker-compose+exec+myservice+sh|code-block|syntax|javascript|4425934|但是，如果您使用不同的yml文件名，如docker-compose-mycompose.yml，则应使用$+docker-compose+-f+docker-compose-mycompose.yml+up启动它。要附加交互式终端，还必须指定yml文件，就像这样：|4425935|$+docker-compose+-f+docker-compose-mycompose.yml+exec+myservice+sh|4425936|entityMap^0|2|3|7|I|Y|J|22|3|2C|9|0|0|B|3|J|S|1G|1F|3D|3|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|12|8|@$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|M|3|N|5|H|7|1B|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|P|$]]

If the <code>yml</code> is called <code>docker-compose.yml</code> it can be launched with a simple <code>$ docker-compose up</code>. The corresponding attachment of a terminal can be simply (consider that the <code>yml</code> has specified a service called <code>myservice</code>):

<pre><code>$ docker-compose exec myservice sh

</code></pre>

However, if you are using a different <code>yml</code> file name, such as <code>docker-compose-mycompose.yml</code>, it should be launched using <code>$ docker-compose -f docker-compose-mycompose.yml up</code>. To attach an interactive terminal you have to specify the <code>yml</code> file too, just like:

<pre><code>$ docker-compose -f docker-compose-mycompose.yml exec myservice sh

</code></pre>

blocks|key|4426064|text|这是一个老问题的补充，因为我上一次才有这个例子。sh和bash之间的区别。因此，对于某些情况，bash可能不起作用，而只有sh起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4426065|所以你可以：docker-compose+exec+CONTAINER_NAME+sh|offset|length|style|CODE|4426066|在大多数情况下：docker-compose+exec+CONTAINER_NAME+bash|4426067|使用。|4426068|如果你有时间的话。这里很好地解释了sh和bash之间的区别：https://www.baeldung.com/linux/sh-vs-bash|4426069|entityMap|0|LINK|mutability|MUTABLE|url|https://www.baeldung.com/linux/sh-vs-bash^0|0|6|11|0|8|13|0|0|U|15|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@$D|X|E|Y|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|Z|8|@$D|10|E|11|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@$D|14|E|15|1|16]]|A|$]]|$1|N|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

A addition to this old question, as I only had the case last time. The difference between sh and bash. So it can happen that for some bash doesn't work and only sh does.
So you can:
<code>docker-compose exec CONTAINER_NAME sh</code>
and in most cases: <code>docker-compose exec CONTAINER_NAME bash</code>
use.
If you have time. The difference between sh and bash is well explained here:
<a href="https://www.baeldung.com/linux/sh-vs-bash" rel="noreferrer">https://www.baeldung.com/linux/sh-vs-bash</a>

blocks|key|4425962|text|我更喜欢|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4425963|docker-compose+exec+my_container_name+bash|code-block|syntax|javascript|4425964|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I prefer
<pre class="lang-sh prettyprint-override"><code>docker-compose exec my_container_name bash
</code></pre>

blocks|key|4425889|text|您可以在命令行上执行docker-compose+exec+SERVICE_NAME+sh。SERVICE_NAME在您的docker-compose.yml中定义。例如,|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4425890|services:
++++zookeeper:
++++++++image:+wurstmeister/zookeeper
++++++++ports:
++++++++++-+"2181:2181"|code-block|syntax|javascript|4425891|SERVICE_NAME应该是"zookeeper“。|4425892|entityMap^0|A|Z|1A|C|1P|I|0|0|0|C|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|N|$]]

You can do <code>docker-compose exec SERVICE_NAME sh</code> on the command line. The <code>SERVICE_NAME</code> is defined in your <code>docker-compose.yml</code>. For example,

<pre><code>services:
 zookeeper:
 image: wurstmeister/zookeeper
 ports:
 - "2181:2181"
</code></pre>

The <code>SERVICE_NAME</code> would be "zookeeper".

blocks|key|4425970|text|根据documentation+->+https://docs.docker.com/compose/reference/run/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4425971|您可以使用此docker-compose+run+--rm+app+bash|style|CODE|4425972|app是docker-compose.yml中服务的名称|4425973|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/compose/reference/run/^0|J|1A|0|0|6|W|0|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]]|9|@]|C|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

According to documentation -&gt; <a href="https://docs.docker.com/compose/reference/run/" rel="nofollow noreferrer">https://docs.docker.com/compose/reference/run/</a>
You can use this <code>docker-compose run --rm app bash</code>
[app] is the name of your service in docker-compose.yml

Is there any way to start an interactive shell in a container using Docker Compose only? I've tried something like this, in my docker-compose.yml:
<pre><code>myapp:
 image: alpine:latest
 entrypoint: /bin/sh
</code></pre>
When I start this container using docker-compose up it's exited immediately. Are there any flags I can add to the <code>entrypoint</code> command, or as an additional option to <code>myapp</code>, to start an interactive shell?
I know there are native docker command options to achieve this, just curious if it's possible using only Docker Compose, too.

Interactive shell using Docker Compose

容器

Docker

有没有办法只使用Docker Compose在容器中启动交互式shell？我在我的docker-compose.yml中尝试过这样的东西：myapp:  image: alpine:latest  entrypoint: /bin/sh当我使用docker-compose up启动这个容器时，它会立即退出。有没有什么标志可以添加到entrypoint命令中，或者作为myapp的附加选项来启动交互式

问使用Docker Compose的交互式shell
EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Docker Compose的交互式shellEN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Docker Compose的交互式shell
EN