entityMap|0|type|LINK|mutability|MUTABLE|data|url|http://phusion.github.io/baseimage-docker/#intro|1|https://docs.docker.com/engine/examples/running_ssh_service/|blocks|key|c7cdt|text|更新：正如在下面的答案Ctrl%2Bp中提到的，Ctrl%2Bq现在将把交互模式转换为守护程序模式。|unstyled|depth|inlineStyleRanges|entityRanges|bkubm|——————————————————————————————————————|ddqat|Well+Ctrl%2BC+(或Ctrl%2B)应该把你从容器中分离出来，但是它会杀死容器因为您的主进程是一个bash。|ecf8p|给你上一堂关于码头的课。容器不是真正的全功能操作系统。当您运行一个容器时，您启动的进程将采用PID为1并采用init能力。因此，当进程终止时，守护进程将停止容器，直到启动新进程(通过docker+start)+(有关此问题的更多说明http://phusion.github.io/baseimage-docker/#intro)|offset|length|style|UNDERLINE|3q76i|如果您想要一个始终以分离模式运行的容器，我建议您使用|5mjp5|docker+run+-d+foo|code-block|syntax|javascript|7sbu4|容器上的ssh服务器。(最简单的方法是遵循dockerizing+openssh教程|bf89o|https://docs.docker.com/engine/examples/running_ssh_service/)|8lqeu|或者，您可以通过以下方式重新启动您的容器|fsfcn|docker+start+foo|9v321|(默认分离)^0|0|0|0|38|1C|38|1C|0|0|0|0|0|0|1O|0|1O|1|0|0|0^^$0|$1|$2|3|4|5|6|$7|8]]|9|$2|3|4|5|6|$7|A]]]|B|@$C|D|E|F|2|G|H|1B|I|@]|J|@]|6|$]]|$C|K|E|L|2|G|H|1C|I|@]|J|@]|6|$]]|$C|M|E|N|2|G|H|1D|I|@]|J|@]|6|$]]|$C|O|E|P|2|G|H|1E|I|@$Q|1F|R|1G|S|T]]|J|@$Q|1H|R|1I|C|1J]]|6|$]]|$C|U|E|V|2|G|H|1K|I|@]|J|@]|6|$]]|$C|W|E|X|2|Y|H|1L|I|@]|J|@]|6|$Z|10]]|$C|11|E|12|2|G|H|1M|I|@]|J|@]|6|$]]|$C|13|E|14|2|G|H|1N|I|@$Q|1O|R|1P|S|T]]|J|@$Q|1Q|R|1R|C|1S]]|6|$]]|$C|15|E|16|2|G|H|1T|I|@]|J|@]|6|$]]|$C|17|E|18|2|Y|H|1U|I|@]|J|@]|6|$Z|10]]|$C|19|E|1A|2|G|H|1V|I|@]|J|@]|6|$]]]]

Update: As mentioned in below answers <kbd>Ctrl</kbd>+<kbd>p</kbd>, <kbd>Ctrl</kbd>+<kbd>q</kbd> will now turn interactive mode into daemon mode.

<hr>

Well <kbd>Ctrl</kbd>+<kbd>C</kbd> (or <kbd>Ctrl</kbd>+<kbd>\</kbd>) should detach you from the container but it will kill the container because your main process is a bash.

A little lesson about docker.
The container is not a real full functional OS. When you run a container the process you launch take the PID 1 and assume init power. So when that process is terminated the daemon stop the container until a new process is launched (via docker start) (More explanation on the matter <a href="http://phusion.github.io/baseimage-docker/#intro" rel="noreferrer">http://phusion.github.io/baseimage-docker/#intro</a>)

If you want a container that run in detached mode all the time, i suggest you use

<pre><code>docker run -d foo
</code></pre>

With an ssh server on the container. (easiest way is to follow the dockerizing openssh tutorial <a href="https://docs.docker.com/engine/examples/running_ssh_service/" rel="noreferrer">https://docs.docker.com/engine/examples/running_ssh_service/</a>)

Or you can just relaunch your container via

<pre><code>docker start foo
</code></pre>

(it will be detached by default)

entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://docs.docker.com/v1.7/articles/basics/#running-an-interactive-shell|blocks|key|dnqsv|text|输入Ctrl%2Bp，然后输入Ctrl%2Bq。它将帮助您将交互模式转换为守护程序模式。|unstyled|depth|inlineStyleRanges|entityRanges|41osq|请参见https://docs.docker.com/v1.7/articles/basics/#running-an-interactive-shell。|offset|length|style|UNDERLINE|ds49p|#+To+detach+the+tty+without+exiting+the+shell,
#+use+the+escape+sequence+Ctrl-p+%2B+Ctrl-q
#+note:+This+will+continue+to+exist+in+a+stopped+state+once+exited+(see+"docker+ps+-a")|code-block|syntax|javascript^0|0|3|22|3|22|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|T|G|@]|H|@]|6|$]]|$A|I|C|J|2|E|F|U|G|@$K|V|L|W|M|N]]|H|@$K|X|L|Y|A|Z]]|6|$]]|$A|O|C|P|2|Q|F|10|G|@]|H|@]|6|$R|S]]]]

Type <kbd>Ctrl</kbd>+<kbd>p</kbd> then <kbd>Ctrl</kbd>+<kbd>q</kbd>. It will help you to turn interactive mode to daemon mode.

See <a href="https://docs.docker.com/v1.7/articles/basics/#running-an-interactive-shell" rel="noreferrer">https://docs.docker.com/v1.7/articles/basics/#running-an-interactive-shell</a>.

<pre><code># To detach the tty without exiting the shell,
# use the escape sequence Ctrl-p + Ctrl-q
# note: This will continue to exist in a stopped state once exited (see "docker ps -a")
</code></pre>

entityMap|blocks|key|chuos|text|我认为阿什温的答案是最正确的，我以前的答案如下。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|8mr96|——————————————————————————————————————|2lim2|我想在这里添加另一个选项，即按如下方式运行容器|48d1u|​|5uvrh|docker+run+-dti+foo+bash|code-block|syntax|javascript|b3qhr|然后，您可以进入容器并使用以下命令运行bash|c44rl|docker+exec+-ti+ID_of_foo+bash|4t5nk|无需安装sshd+:)^0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|T|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|U|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|V|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|W|9|@]|A|@]|B|$]]|$2|I|4|J|6|K|8|X|9|@]|A|@]|B|$L|M]]|$2|N|4|O|6|7|8|Y|9|@]|A|@]|B|$]]|$2|P|4|Q|6|K|8|Z|9|@]|A|@]|B|$L|M]]|$2|R|4|S|6|7|8|10|9|@]|A|@]|B|$]]]]

I consider Ashwin's answer to be the most correct, my old answer is below.
<hr>
I'd like to add another option here which is to run the container as follows

<pre><code>docker run -dti foo bash
</code></pre>

You can then enter the container and run bash with

<pre><code>docker exec -ti ID_of_foo bash
</code></pre>

No need to install sshd :)

entityMap|blocks|key|1o797|text|如果你做了"docker+attach“容器id，你就进入了容器。要退出容器而不停止容器，你需要输入Ctrl%2BP%2BQ|type|unstyled|depth|inlineStyleRanges|entityRanges|data^0^^$0|$]|1|@$2|3|4|5|6|7|8|C|9|@]|A|@]|B|$]]]]

If you do "docker attach "container id" you get into the container.
To exit from the container without stopping the container you need to enter <kbd>Ctrl</kbd>+<kbd>P</kbd>+<kbd>Q</kbd>

entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://docs.docker.com/engine/reference/commandline/attach/#override-the-detach-sequence|blocks|key|99cfk|text|从交互式容器分离的缺省方法是Ctrl%2BP+Ctrl%2BQ，但在运行新容器或附加到现有容器时，可以使用the+--detach-keys+flag.。|unstyled|depth|inlineStyleRanges|offset|length|style|UNDERLINE|entityRanges^0|1D|M|1D|M|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|M|G|@$H|N|I|O|J|K]]|L|@$H|P|I|Q|A|R]]|6|$]]]]

The default way to detach from an interactive container is <kbd>Ctrl</kbd>+<kbd>P</kbd> <kbd>Ctrl</kbd>+<kbd>Q</kbd>, but you can override it when running a new container or attaching to existing container using <a href="https://docs.docker.com/engine/reference/commandline/attach/#override-the-detach-sequence" rel="noreferrer">the --detach-keys flag</a>.

entityMap|blocks|key|98esp|text|尝试使用CTRL%2BP、CTRL%2BQ将交互模式转换为守护进程。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1o8le|如果这不起作用，并且您通过docker+attach，您可以通过杀死docker+attach流程。|offset|length|style|CODE|7j8jk|更好的方法是使用sig-proxy参数来避免将CTRL%2BC传递给您的容器：|9mpf2|docker+attach+--sig-proxy=false+[container-name]|code-block|syntax|javascript|3hham|同样的选项可用于docker+run命令。^0|0|D|D|Y|D|0|0|0|8|A^^$0|$]|1|@$2|3|4|5|6|7|8|R|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|S|9|@$E|T|F|U|G|H]|$E|V|F|W|G|H]]|A|@]|B|$]]|$2|I|4|J|6|7|8|X|9|@]|A|@]|B|$]]|$2|K|4|L|6|M|8|Y|9|@]|A|@]|B|$N|O]]|$2|P|4|Q|6|7|8|Z|9|@$E|10|F|11|G|H]]|A|@]|B|$]]]]

Try <kbd>CTRL</kbd>+<kbd>P</kbd>,<kbd>CTRL</kbd>+<kbd>Q</kbd> to turn interactive mode to daemon.
If this does not work and you attached through <code>docker attach</code>, you can detach by killing the <code>docker attach</code> process.
Better way is to use sig-proxy parameter to avoid passing the <kbd>CTRL</kbd>+<kbd>C</kbd> to your container :
<pre><code>docker attach --sig-proxy=false [container-name]
</code></pre>
Same option is available for <code>docker run</code> command.

entityMap|blocks|key|3or2h|text|我深入研究了这一点，上面所有的答案都是部分正确的。这完全取决于容器是如何启动的。当容器启动时，它可以归结为以下几点：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|daj8m|是否分配了TTY+(-t)|unordered-list-item|offset|length|style|CODE|f01s9|stdin是否保持打开状态(-i)|2f6kc|%5EP%5EQ确实有效，但是仅当-t和-i用于启动容器：|header-two|BOLD|7fivs|[berto@g6]$+docker+run+-ti+-d+--name+test+python:3.6+/bin/bash+-c+'while+[+1+];+do+sleep+30;+done;'
b26e39632351192a9a1a00ea0c2f3e10729b6d3e22f8e0676d6519e15c08b518

[berto@g6]$+docker+attach+test
#+here+I+typed+%5EP%5EQ
read+escape+sequence

#+i'm+back+to+my+prompt
[berto@g6]$+docker+kill+test;+docker+rm+-v+test
test
test|code-block|syntax|javascript|dj33v|ctrl%2Bc确实有效，但是仅当-t(没有-i)用于启动容器：|2230v|[berto@g6]$+docker+run+-t+-d+--name+test+python:3.6+/bin/bash+-c+'while+[+1+];+do+sleep+30;+done;'
018a228c96d6bf2e73cccaefcf656b02753905b9a859f32e60bdf343bcbe834d

[berto@g6]$+docker+attach+test
%5EC

[berto@g6]$|6nq18|分离的第三种方式|1cib1|不过，有一种方法可以在不杀死容器的情况下进行分离；您需要另一个shell。总之，在另一个分离的shell中运行它会让容器继续运行pkill+-9+-f+'docker.*attach'|8ajl3|[berto@g6]$+docker+run+-d+--name+test+python:3.6+/bin/bash+-c+'while+[+1+];+do+sleep+30;+done;'
b26e39632351192a9a1a00ea0c2f3e10729b6d3e22f8e0676d6519e15c08b518

[berto@g6]$+docker+attach+test
#+here+I+typed+%5EP%5EQ+and+doesn't+work
%5EP
#+ctrl%2Bc+doesn't+work+either
%5EC
#+can't+background+either
%5EZ

#+go+to+another+shell+and+run+the+`pkill`+command+above

#+i'm+back+to+my+prompt
[berto@g6]$|d69qc|为什么？因为您正在杀死将您连接到容器的进程，而不是容器本身。^0|0|A|2|0|E|2|0|0|4|D|2|G|2|4|9|F|1|I|6|0|0|0|6|F|2|K|2|6|9|I|2|N|7|0|0|0|1S|S|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|16|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|17|9|@$F|18|G|19|H|I]]|A|@]|B|$]]|$2|J|4|K|6|E|8|1A|9|@$F|1B|G|1C|H|I]]|A|@]|B|$]]|$2|L|4|M|6|N|8|1D|9|@$F|1E|G|1F|H|I]|$F|1G|G|1H|H|I]|$F|1I|G|1J|H|I]|$F|1K|G|1L|H|O]|$F|1M|G|1N|H|O]|$F|1O|G|1P|H|O]]|A|@]|B|$]]|$2|P|4|Q|6|R|8|1Q|9|@]|A|@]|B|$S|T]]|$2|U|4|V|6|N|8|1R|9|@$F|1S|G|1T|H|I]|$F|1U|G|1V|H|I]|$F|1W|G|1X|H|I]|$F|1Y|G|1Z|H|O]|$F|20|G|21|H|O]|$F|22|G|23|H|O]]|A|@]|B|$]]|$2|W|4|X|6|R|8|24|9|@]|A|@]|B|$S|T]]|$2|Y|4|Z|6|N|8|25|9|@]|A|@]|B|$]]|$2|10|4|11|6|7|8|26|9|@$F|27|G|28|H|I]]|A|@]|B|$]]|$2|12|4|13|6|R|8|29|9|@]|A|@]|B|$S|T]]|$2|14|4|15|6|7|8|2A|9|@]|A|@]|B|$]]]]

I dug into this and all the answers above are partially right. It all depends on how the container is launched. It comes down to the following when the container was launched:

<ul>
<li>was a TTY allocated (<code>-t</code>)</li>
<li>was stdin left open (<code>-i</code>)</li>
</ul>

<h2><code>^P^Q</code> does work, BUT only when <code>-t</code> and <code>-i</code> is used to launch the container:</h2>

<pre><code>[berto@g6]$ docker run -ti -d --name test python:3.6 /bin/bash -c 'while [ 1 ]; do sleep 30; done;'
b26e39632351192a9a1a00ea0c2f3e10729b6d3e22f8e0676d6519e15c08b518

[berto@g6]$ docker attach test
# here I typed ^P^Q
read escape sequence

# i'm back to my prompt
[berto@g6]$ docker kill test; docker rm -v test
test
test
</code></pre>

<h2><code>ctrl+c</code> does work, BUT only when <code>-t</code> (without <code>-i</code>) is used to launch the container:</h2>

<pre><code>[berto@g6]$ docker run -t -d --name test python:3.6 /bin/bash -c 'while [ 1 ]; do sleep 30; done;'
018a228c96d6bf2e73cccaefcf656b02753905b9a859f32e60bdf343bcbe834d

[berto@g6]$ docker attach test
^C

[berto@g6]$ 
</code></pre>

<h2>The third way to detach</h2>

There is a way to detach without killing the container though; you need another shell. In summary, running this in another shell detached and left the container running <code>pkill -9 -f 'docker.*attach'</code>:

<pre><code>[berto@g6]$ docker run -d --name test python:3.6 /bin/bash -c 'while [ 1 ]; do sleep 30; done;'
b26e39632351192a9a1a00ea0c2f3e10729b6d3e22f8e0676d6519e15c08b518

[berto@g6]$ docker attach test
# here I typed ^P^Q and doesn't work
^P
# ctrl+c doesn't work either
^C
# can't background either
^Z

# go to another shell and run the `pkill` command above

# i'm back to my prompt
[berto@g6]$
</code></pre>

Why? Because you're killing the process that connected you to the container, not the container itself.

entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://docs.docker.com/engine/reference/commandline/cli/#configuration-files|blocks|key|692oi|text|您可以使用--detach-keys选项docker+attach要覆盖默认的CTRL%2BP，请按CTRL+%2BQ序列(这并不总是有效的)。|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|6qqlc|例如，当您运行docker+attach+--detach-keys="ctrl-a"++test然后按CTRL%2BA键，您将退出容器，而不会终止它。|579f4|其他示例：|cerji|docker+attach+--detach-keys="ctrl-a,x"++test-新闻CTRL%2BA然后X退出|unordered-list-item|32ats|docker+attach+--detach-keys="a,b,c"++test-新闻A，然后B，然后C退出|528ph|摘自官方文档：|BOLD|fqjgs|如果需要，您可以配置覆盖Docker键序列以进行分离。如果Docker默认序列与您用于其他应用程序的按键序列冲突，这将非常有用。有两种方法可以定义您自己的分离键序列，作为每个容器的重写或作为整个配置上的配置属性。|f2veh|若要重写单个容器的序列，请使用--detach-keys=""使用docker+attach命令标记。的格式为字母[a-Z]，或ctrl-与以下任意一项相结合：|4pqlq|a-z+(单个小写字母字符)|1drpa|@(在符号处)|47dmu|[(左括号)|460t3|\(两个反斜杠)|antvq|_(下划线)|98sa0|%5E(插入符号)|8fdlv|这些a,+ctrl-a,+X，或者ctrl-\\值都是有效键序列的示例。若要为所有容器配置不同的配置缺省键序列，请参见Configuration文件节。|UNDERLINE|c9ecb|注意:这是从docker版本1.10%2B开始工作的(在回答这个问题时，当前版本是18.03)^0|5|D|K|D|0|7|16|0|0|0|18|1B|6|1J|1|0|0|15|18|1|1C|1|1G|1|0|0|7|0|0|F|G|1L|5|1S|5|0|0|0|0|0|0|0|2|1|5|6|D|1|H|7|1N|D|1N|D|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|1J|G|@$H|1K|I|1L|J|K]|$H|1M|I|1N|J|K]]|L|@]|6|$]]|$A|M|C|N|2|E|F|1O|G|@$H|1P|I|1Q|J|K]]|L|@]|6|$]]|$A|O|C|P|2|E|F|1R|G|@]|L|@]|6|$]]|$A|Q|C|R|2|S|F|1S|G|@$H|1T|I|1U|J|K]|$H|1V|I|1W|J|K]|$H|1X|I|1Y|J|K]]|L|@]|6|$]]|$A|T|C|U|2|S|F|1Z|G|@$H|20|I|21|J|K]|$H|22|I|23|J|K]|$H|24|I|25|J|K]|$H|26|I|27|J|K]]|L|@]|6|$]]|$A|V|C|W|2|E|F|28|G|@$H|29|I|2A|J|X]]|L|@]|6|$]]|$A|Y|C|Z|2|E|F|2B|G|@]|L|@]|6|$]]|$A|10|C|11|2|E|F|2C|G|@$H|2D|I|2E|J|K]|$H|2F|I|2G|J|K]|$H|2H|I|2I|J|K]]|L|@]|6|$]]|$A|12|C|13|2|S|F|2J|G|@]|L|@]|6|$]]|$A|14|C|15|2|S|F|2K|G|@]|L|@]|6|$]]|$A|16|C|17|2|S|F|2L|G|@]|L|@]|6|$]]|$A|18|C|19|2|S|F|2M|G|@]|L|@]|6|$]]|$A|1A|C|1B|2|S|F|2N|G|@]|L|@]|6|$]]|$A|1C|C|1D|2|S|F|2O|G|@]|L|@]|6|$]]|$A|1E|C|1F|2|E|F|2P|G|@$H|2Q|I|2R|J|K]|$H|2S|I|2T|J|K]|$H|2U|I|2V|J|K]|$H|2W|I|2X|J|K]|$H|2Y|I|2Z|J|1G]]|L|@$H|30|I|31|A|32]]|6|$]]|$A|1H|C|1I|2|E|F|33|G|@]|L|@]|6|$]]]]

You can use the <code>--detach-keys</code> option when you run <code>docker attach</code> to override the default <kbd>CTRL</kbd>+<kbd>P</kbd>, <kbd>CTRL</kbd> + <kbd>Q</kbd> sequence (that doesn't always work).

For example, when you run <code>docker attach --detach-keys="ctrl-a" test</code> and you press <kbd>CTRL</kbd>+<kbd>A</kbd> you will exit the container, without killing it.

Other examples:

<ul>
<li><code>docker attach --detach-keys="ctrl-a,x" test</code> - press <code>CTRL+A</code> and then <code>X</code> to exit</li>
<li><code>docker attach --detach-keys="a,b,c" test</code> - press <code>A</code>, then <code>B</code>, then <code>C</code> to exit</li>
</ul>

Extract from the official documentation:

If you want, you can configure an override the Docker key sequence for detach. This is useful if the Docker default sequence conflicts with key sequence you use for other applications. There are two ways to define your own detach key sequence, as a per-container override or as a configuration property on your entire configuration.

To override the sequence for an individual container, use the <code>--detach-keys="&lt;sequence&gt;"</code> flag with the docker attach command. The format of the <code>&lt;sequence&gt;</code> is either a letter <code>[a-Z]</code>, or the <code>ctrl-</code> combined with any of the following:

<ul>
<li>a-z (a single lowercase alpha character )</li>
<li>@ (at sign)</li>
<li>[ (left bracket)</li>
<li>\ (two backward slashes)</li>
<li>_ (underscore)</li>
<li>^ (caret)</li>
</ul>

These <code>a</code>, <code>ctrl-a</code>, <code>X</code>, or <code>ctrl-\\</code> values are all examples of valid key sequences. To configure a different configuration default key sequence for all containers, see <a href="https://docs.docker.com/engine/reference/commandline/cli/#configuration-files" rel="noreferrer">Configuration</a> file section.

Note: This works since docker version 1.10+ (at the time of this answer, the current version is 18.03)

entityMap|blocks|key|4upnr|text|如果您只想查看从容器中运行的进程的输出，您可以执行简单的docker+container+logs+-f+。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|60cf2|The-f标志使得容器的输出为followed并实时更新。对调试或监控非常有用。^0|S|P|0|3|2|F|8^^$0|$]|1|@$2|3|4|5|6|7|8|I|9|@$A|J|B|K|C|D]]|E|@]|F|$]]|$2|G|4|H|6|7|8|L|9|@$A|M|B|N|C|D]|$A|O|B|P|C|D]]|E|@]|F|$]]]]

If you just want see the output of the process running from within the container, you can do a simple <code>docker container logs -f &lt;container id&gt;</code>. 

The <code>-f</code> flag makes it so that the output of the container is <code>followed</code> and updated in real-time. Very useful for debugging or monitoring.

entityMap|blocks|key|7aort|text|旧帖子，但只需退出，然后重新启动...问题是，如果您在windows计算机上，Ctrl+p或Ctrl+P绑定到打印...退出启动容器应该不会有任何伤害|type|unstyled|depth|inlineStyleRanges|entityRanges|data^0^^$0|$]|1|@$2|3|4|5|6|7|8|C|9|@]|A|@]|B|$]]]]

Old post but just exit then start it again... the issue is if you are on a windows machine Ctrl p or Ctrl P are tied to print... exiting the starting the container should not hurt anything

entityMap|blocks|key|c02li|text|您可以通过发送SEGKILL简单地杀死docker+cli进程。如果您使用以下命令启动容器|type|unstyled|depth|inlineStyleRanges|entityRanges|data|8rmjb|docker+run+-it+some/container|offset|length|style|CODE|549nf|你可以得到它的pid|8j5rn|ps+-aux+%7C+grep+docker|5nf9n|user+++1234++0.3++0.6+1357948+54684+pts/2+++Sl%2B++15:09+++0:00+docker+run+-it+some/container|code-block|syntax|javascript|b7bu9|比方说它是1234，你可以用下面的命令“分离”它|9okf3|kill+-9+1234|er71k|这在某种程度上是一种黑客行为，但它是有效的！^0|0|0|T|0|0|0|L|0|0|0|0|C|0^^$0|$]|1|@$2|3|4|5|6|7|8|X|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|Y|9|@$E|Z|F|10|G|H]]|A|@]|B|$]]|$2|I|4|J|6|7|8|11|9|@]|A|@]|B|$]]|$2|K|4|L|6|7|8|12|9|@$E|13|F|14|G|H]]|A|@]|B|$]]|$2|M|4|N|6|O|8|15|9|@]|A|@]|B|$P|Q]]|$2|R|4|S|6|7|8|16|9|@]|A|@]|B|$]]|$2|T|4|U|6|7|8|17|9|@$E|18|F|19|G|H]]|A|@]|B|$]]|$2|V|4|W|6|7|8|1A|9|@]|A|@]|B|$]]]]

You can simply kill docker cli process by sending SEGKILL. If you started the container with
<code>docker run -it some/container</code>
You can get it's pid
<code>ps -aux | grep docker</code>
<pre><code>user 1234 0.3 0.6 1357948 54684 pts/2 Sl+ 15:09 0:00 docker run -it some/container
</code></pre>
let's say it's 1234, you can &quot;detach&quot; it with
<code>kill -9 1234</code>
It's somewhat of a hack but it works!

entityMap|blocks|key|8m2n2|text|在Docker容器中，必须至少运行一个进程，那么只有容器将在后台运行docker镜像(ubuntu、httd..etc，不管它是什么)，而不退出|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|e91mo|例如在ubuntu对接镜像中，|7hut0|要创建具有分离模式的新容器(至少在进程上运行后台)，|9o4q4|docker+run+-d+-i+-t+f63181f19b2f+/bin/bash|code-block|syntax|javascript|5gcbs|它将为这个镜像(Ubuntu)+id创建一个新容器f63181f19b2f。容器将在分离模式下运行(在后台运行)，此时会有一个小进程ttybash+shell将在后台运行。因此，容器将继续运行，直到bash+shell进程被终止。|CODE|mkou|要附加到正在运行的后台容器，请使用|91bbd|docker+attach++b1a0873a8647|85j9m|如果您想在不退出的情况下从容器中分离(而不终止bash+shell)，默认情况下，您可以使用ctrl-p,q。它将离开容器而不退出容器(运行后台。这意味着在不杀死bash+shell的情况下)。|f20cr|您可以在附加到容器时传递自定义命令。|bc2h0|docker+attach+--detach-keys="ctrl-s"+b1a0873a8647|9cmr9|这一次ctrl-p,q转义序列不起作用。相反，ctrl-s将用于退出容器。你可以传递任何密钥，例如，(ctrl-*)^0|0|L|0|0|E|0|0|Q|0|0|P|C|1U|3|0|0|H|0|0|1A|8|1A|8|0|0|I|0|0|3|8|N|6|1E|8|3|8|N|6|1E|8^^$0|$]|1|@$2|3|4|5|6|7|8|14|9|@$A|15|B|16|C|D]]|E|@]|F|$]]|$2|G|4|H|6|7|8|17|9|@$A|18|B|19|C|D]]|E|@]|F|$]]|$2|I|4|J|6|7|8|1A|9|@$A|1B|B|1C|C|D]]|E|@]|F|$]]|$2|K|4|L|6|M|8|1D|9|@]|E|@]|F|$N|O]]|$2|P|4|Q|6|7|8|1E|9|@$A|1F|B|1G|C|R]|$A|1H|B|1I|C|R]]|E|@]|F|$]]|$2|S|4|T|6|7|8|1J|9|@$A|1K|B|1L|C|D]]|E|@]|F|$]]|$2|U|4|V|6|M|8|1M|9|@]|E|@]|F|$N|O]]|$2|W|4|X|6|7|8|1N|9|@$A|1O|B|1P|C|D]|$A|1Q|B|1R|C|R]]|E|@]|F|$]]|$2|Y|4|Z|6|7|8|1S|9|@$A|1T|B|1U|C|D]]|E|@]|F|$]]|$2|10|4|11|6|M|8|1V|9|@]|E|@]|F|$N|O]]|$2|12|4|13|6|7|8|1W|9|@$A|1X|B|1Y|C|D]|$A|1Z|B|20|C|D]|$A|21|B|22|C|D]|$A|23|B|24|C|R]|$A|25|B|26|C|R]|$A|27|B|28|C|R]]|E|@]|F|$]]]]

In Docker container atleast one process must be run, then only the container will be running the docker image(ubuntu,httd..etc, whatever it is) at background without exiting
For example in ubuntu docker image ,
To create a new container with detach mode (running background atleast on process),
<pre><code>docker run -d -i -t f63181f19b2f /bin/bash
</code></pre>
it will create a new contain for this image(ubuntu) id <code>f63181f19b2f</code> . The container will run in the detached mode (running in background) at that time a small process <code>tty</code> bash shell will be running at background. so, container will keep on running untill the bash shell process will killed.
To attach to the running background container,use
<pre><code>docker attach b1a0873a8647
</code></pre>
if you want to detach from container without exiting(without killing the bash shell),
By default , you can use <code>ctrl-p,q</code>. it will come out of container without exiting from the container(running background. that means without killing the bash shell).
You can pass the custom command during attach time to container,
<pre><code>docker attach --detach-keys=&quot;ctrl-s&quot; b1a0873a8647
</code></pre>
this time <code>ctrl-p,q</code> escape sequence won't work. instead, <code>ctrl-s</code> will work for exiting from container. you can pass any key eg, <code>(ctrl-*)</code>

In Docker 1.1.2 (latest), what's the correct way to detach from a container without stopping it?

So for example, if I try:

<ul>
<li><code>docker run -i -t foo /bin/bash</code> or</li>
<li><code>docker attach foo</code> (for already running container)</li>
</ul>

both of which get me to a terminal in the container, how do I exit the container's terminal without stopping it?

<code>exit</code> and <code>CTR+C</code> both stop the container.

Correct way to detach from a container without stopping it

服务器

容器

Docker

Ubuntu

 在Docker 1.1.2 (最新版本)中，在不停止容器的情况下，从容器分离的正确方法是什么？ 例如，如果我尝试： docker run -i -t foo /bin/bash或者 docker attach foo(对于已经运行的容器) 这两种方法都会将我带到容器中的终端，如何在不停止的情况下退出容器的终端？ ex...

问在不停止容器的情况下从容器中分离的正确方法
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在不停止容器的情况下从容器中分离的正确方法EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在不停止容器的情况下从容器中分离的正确方法
EN