blocks|key|269527|text|编辑:现在可以使用docker+exec+-it+"id+of+running+container"+bash+(doc)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|269528|以前，这个问题的答案是：|269529|如果您确实必须这样做，并且您处于调试环境中，则可以这样做：sudo+lxc-attach+-n+<ID>请注意，id必须是完整的id+(docker+ps+-notrunc)。|269530|然而，我强烈建议不要这样做。|269531|注意：-notrunc已被弃用，将很快被--no-trunc取代。|269532|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/engine/reference/commandline/exec/^0|9|1A|1L|3|0|0|0|T|N|1W|I|0|0|3|8|K|A|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|17|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|18|8|@$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|N|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U]]]]

EDIT: Now you can use <code>docker exec -it "id of running container" bash</code> (<a href="https://docs.docker.com/engine/reference/commandline/exec/" rel="noreferrer">doc</a>)

Previously, the answer to this question was:

If you really must and you are in a debug environment, you can do this: <code>sudo lxc-attach -n &lt;ID&gt;</code>
Note that the id needs to be the full one (<code>docker ps -notrunc</code>).

However, I strongly recommend against this.

notice: <code>-notrunc</code> is deprecated, it will be replaced by <code>--no-trunc</code> soon.

blocks|key|53178|text|在docker+1.3中，有一个新的命令docker+exec。这允许您进入正在运行的docker：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|53179|docker+exec+-it+"id+of+running+container"+bash|code-block|syntax|javascript|53180|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/engine/reference/commandline/exec/^0|K|B|K|B|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@$9|V|A|W|1|X]]|E|$]]|$1|F|3|G|5|H|7|Y|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]]]

With docker 1.3, there is a new command <a href="https://docs.docker.com/engine/reference/commandline/exec/" rel="noreferrer"><code>docker exec</code></a>. This allows you to enter a running docker:

<pre><code>docker exec -it "id of running container" bash
</code></pre>

blocks|key|269646|text|由于事情正在发生变化，目前推荐的访问运行容器的方式是使用nsenter。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|269647|您可以在此github+repository上找到更多信息。但一般来说，您可以像这样使用nsenter：|269648|PID=$(docker+inspect+--format+{{.State.Pid}}+<container_name_or_ID>)
nsenter+--target+$PID+--mount+--uts+--ipc+--net+--pid|code-block|syntax|javascript|269649|或者，您可以使用包装器docker-enter|269650|docker-enter+<container_name_or_ID>|269651|关于这个话题的一个很好的解释可以在杰罗姆·佩塔佐尼的博客上找到：Why+you+don't+need+to+run+sshd+in+your+docker+containers|269652|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/jpetazzo/nsenter|1|http://blog.docker.com/2014/06/why-you-dont-need-to-run-sshd-in-docker/^0|S|7|0|5|H|0|0|0|B|C|0|0|W|1K|1|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@$9|16|A|17|1|18]]|E|$]]|$1|H|3|I|5|J|7|19|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|1D|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|1E|8|@]|D|@$9|1F|A|1G|1|1H]]|E|$]]|$1|S|3|-4|5|6|7|1I|8|@]|D|@]|E|$]]]|T|$U|$5|V|W|X|E|$Y|Z]]|10|$5|V|W|X|E|$Y|11]]]]

Since things are achanging, at the moment the recommended way of accessing a running container is using <code>nsenter</code>.

You can find more information on this <a href="https://github.com/jpetazzo/nsenter">github repository</a>. But in general you can use nsenter like this:

<pre><code>PID=$(docker inspect --format {{.State.Pid}} &lt;container_name_or_ID&gt;)
nsenter --target $PID --mount --uts --ipc --net --pid
</code></pre>

or you can use the wrapper <code>docker-enter</code>:

<pre><code>docker-enter &lt;container_name_or_ID&gt;
</code></pre>

A nice explanation on the topic can be found on Jérôme Petazzoni's blog entry:
<a href="http://blog.docker.com/2014/06/why-you-dont-need-to-run-sshd-in-docker/">Why you don't need to run sshd in your docker containers</a>

blocks|key|269711|text|您可以使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|269712|docker+exec+-it+<container_name>+bash|code-block|syntax|javascript|269713|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|$]]

You can use

<pre><code>docker exec -it &lt;container_name&gt; bash
</code></pre>

blocks|key|269613|text|实际上，有一种方法可以在容器中拥有一个shell。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|269614|假设您的/root/run.sh启动了进程、进程管理器(supervisor)或其他任何东西。|offset|length|style|CODE|269615|使用一些gnu-screen技巧创建/root/runme.sh：|269616|#+Spawn+a+screen+with+two+tabs
screen+-AdmS+'main'+/root/run.sh
screen+-S+'main'+-X+screen+bash+-l
screen+-r+'main'|code-block|syntax|javascript|269617|现在，您在选项卡0中有自己的守护进程，在选项卡1中有一个交互式shell。docker+attach可以随时查看容器内部发生的情况。|269618|另一个建议是使用所有必要的工具在生产图像的顶部创建一个“开发包”图像，包括这个屏幕技巧。|269619|entityMap^0|0|4|C|0|I|E|0|0|11|D|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@$D|Z|E|10|F|G]]|9|@]|A|$]]|$1|J|3|K|5|L|7|11|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|12|8|@$D|13|E|14|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|T|$]]

There is actually a way to have a shell in the container.

Assume your <code>/root/run.sh</code> launches the process, process manager (supervisor), or whatever.

Create <code>/root/runme.sh</code> with some gnu-screen tricks:

<pre><code># Spawn a screen with two tabs
screen -AdmS 'main' /root/run.sh
screen -S 'main' -X screen bash -l
screen -r 'main'
</code></pre>

Now, you have your daemons in tab 0, and an interactive shell in tab 1. <code>docker attach</code> at any time to see what's happening inside the container.

Another advice is to create a "development bundle" image on top of the production image with all the necessary tools, including this screen trick.

blocks|key|269682|text|有两种方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|269683|使用附加|269684|$+sudo+docker+attach+665b4a1e17b6+#by+ID|code-block|syntax|javascript|269685|使用exec|269686|$+sudo+docker+exec+-+-t+665b4a1e17b6+#by+ID|269687|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

There are two ways.

With attach

<pre><code>$ sudo docker attach 665b4a1e17b6 #by ID
</code></pre>

With exec 

<pre><code>$ sudo docker exec - -t 665b4a1e17b6 #by ID
</code></pre>

blocks|key|269555|text|如果目标是检查应用程序的日志，这篇文章展示了启动tomcat并将日志作为CMD的一部分。tomcat日志在主机上使用“docker+logs+containerid”可用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|269556|http://blog.trifork.com/2013/08/15/using-docker-to-efficiently-create-multiple-tomcat-instances/|offset|length|269557|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2O|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

If the goal is to check on the application's logs, this post shows starting up tomcat and tailing the log as part of CMD. The tomcat log is available on the host using 'docker logs containerid'.

<a href="http://blog.trifork.com/2013/08/15/using-docker-to-efficiently-create-multiple-tomcat-instances/" rel="nofollow">http://blog.trifork.com/2013/08/15/using-docker-to-efficiently-create-multiple-tomcat-instances/</a>

blocks|key|53215|text|在运行容器时，指定名称非常有用。你不需要引用container_id。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|53216|docker+run+--name+container_name+yourimage++docker+exec+-it+container_name+bash|offset|length|style|CODE|53217|entityMap^0|0|0|27|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

It's useful assign name when running container. You don't need refer container_id.

<code>docker run --name container_name yourimage 
docker exec -it container_name bash</code>

blocks|key|53239|text|首先，通过以下方式获取所需容器的容器id|type|unstyled|depth|inlineStyleRanges|entityRanges|data|53240|docker+ps|code-block|syntax|javascript|53241|你会得到类似这样的结果：|53242|CONTAINER+ID++++++++IMAGE++++++++++++++++++COMMAND+++++++++++++CREATED+++++++++++++STATUS++++++++++++++++++++++++++PORTS++++++++++++++++++++NAMES
3ac548b6b315++++++++frontend_react-web+++++"npm+run+start"+++++48+seconds+ago++++++Up+47+seconds+++++++++++++++++++0.0.0.0:3000->3000/tcp+++frontend_react-web_1|53243|现在复制这个容器id并运行以下命令：|53244|docker+exec+-it+container_id+sh

docker+exec+-it+3ac548b6b315+sh|53245|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|$]]

first, get the container id of the desired container by 

<pre><code>docker ps
</code></pre>

you will get something like this:

<pre><code>CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
3ac548b6b315 frontend_react-web "npm run start" 48 seconds ago Up 47 seconds 0.0.0.0:3000-&gt;3000/tcp frontend_react-web_1

</code></pre>

now copy this container id and run the following command:

<pre><code>docker exec -it container_id sh

docker exec -it 3ac548b6b315 sh

</code></pre>

blocks|key|269568|text|也许你和我一样被误导了，在开发容器时从VM的角度思考。我的建议是:尽量不要这样做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|269569|容器就像任何其他进程一样。实际上，出于调试目的，您可能希望“附加”到它们(想想/proc//env或strace+-p+)，但这是一个非常特殊的情况。|269570|通常你只是“运行”这个过程，所以如果你想修改配置或者读取日志，只要创建一个新的容器，并确保你通过共享目录，写到stdout+(这样docker+logs就可以工作)或者类似的东西来写日志。|269571|出于调试目的，您可能希望启动一个shell，然后启动您的代码，然后按CTRL-p+%2B+CTRL-q使shell保持不变。通过这种方式，您可以使用以下命令重新附加：|269572|docker+attach+<container_id>|code-block|syntax|javascript|269573|如果您想要调试容器，因为它正在做一些您不希望它做的事情，那么试着调试它：https://serverfault.com/questions/596994/how-can-i-debug-a-docker-container-initialization|offset|length|269574|entityMap|0|LINK|mutability|MUTABLE|url|https://serverfault.com/questions/596994/how-can-i-debug-a-docker-container-initialization^0|0|0|0|0|0|10|2I|0|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|6|7|10|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|11|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|12|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|13|8|@]|9|@$O|14|P|15|1|16]]|A|$]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

Maybe you were mislead like myself into thinking in terms of VMs when developing containers. My advice: Try not to.

Containers are just like any other process. Indeed you might want to "attach" to them for debugging purposes (think of /proc//env or strace -p ) but that's a very special case.

Normally you just "run" the process, so if you want to modify the configuration or read the logs, just create a new container and make sure you write the logs outside of it by sharing directories, writing to stdout (so docker logs works) or something like that.

For debugging purposes you might want to start a shell, then your code, then press CTRL-p + CTRL-q to leave the shell intact. This way you can reattach using:

<pre><code>docker attach &lt;container_id&gt;
</code></pre>

If you want to debug the container because it's doing something you haven't expect it to do, try to debug it: <a href="https://serverfault.com/questions/596994/how-can-i-debug-a-docker-container-initialization">https://serverfault.com/questions/596994/how-can-i-debug-a-docker-container-initialization</a>

blocks|key|269480|text|不是的。这是不可能的。如果需要，可以使用supervisord之类的命令获取ssh服务器。不过，我很怀疑有没有必要。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|269481|entityMap^0|K|B|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

No. This is not possible. Use something like <code>supervisord</code> to get an ssh server if that's needed. Although, I definitely question the need.

I was naively expecting this command to run a bash shell in a running container : 

<pre><code>docker run "id of running container" /bin/bash
</code></pre>

it looks like it's not possible, I get the error : 

<pre><code>2013/07/27 20:00:24 Internal server error: 404 trying to fetch remote history for 27d757283842
</code></pre>

So, if I want to run bash shell in a running container (ex. for diagnosis purposes)

do I have to run an SSH server in it and loggin via ssh ?

Is it possible to start a shell session in a running container (without ssh)

我天真地期望这个命令能在运行的容器中运行bash shell：docker run "id of running container" /bin/bash看起来这是不可能的，我得到了错误：2013/07/27 20:00:24 Internal server error: 404 trying to fetch remote history for 27d757283842因此，如果我想在运行的容

问是否可以在运行的容器中启动shell会话(没有ssh)？
EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否可以在运行的容器中启动shell会话(没有ssh)？EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否可以在运行的容器中启动shell会话(没有ssh)？
EN