本文翻译自：Is it possible to start a shell session in a running container (without ssh)

I was naively expecting this command to run a bash shell in a running container : 我天真地期望这个命令在一个正在运行的容器中运行一个bash shell：

docker run "id of running container" /bin/bash

it looks like it's not possible, I get the error : 它看起来不可能，我得到错误：

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

So, if I want to run bash shell in a running container (ex. for diagnosis purposes) 所以，如果我想在一个正在运行的容器中运行bash shell（例如用于诊断目的）

do I have to run an SSH server in it and loggin via ssh ? 我必须在其中运行SSH服务器并通过ssh登录吗？

---

#1楼

参考：https://stackoom.com/question/1D7ZR/是否可以在正在运行的容器中启动shell会话-没有ssh

---

#2楼

No. This is not possible. 不，这是不可能的。 Use something like supervisord to get an ssh server if that's needed. 如果需要，可以使用supervisord东西来获取ssh服务器。 Although, I definitely question the need. 虽然，我绝对质疑需要。

---

#3楼

EDIT: Now you can use docker exec -it "id of running container" bash ( doc ) 编辑：现在你可以使用docker exec -it "id of running container" bash （ doc ）

Previously, the answer to this question was: 以前，这个问题的答案是：

If you really must and you are in a debug environment, you can do this: sudo lxc-attach -n <ID> Note that the id needs to be the full one ( docker ps -notrunc ). 如果你真的必须并且你在调试环境中，你可以这样做： sudo lxc-attach -n <ID>注意id必须是完整的（ docker ps -notrunc ）。

However, I strongly recommend against this. 但是，我强烈建议不要这样做。

notice: -notrunc is deprecated, it will be replaced by --no-trunc soon. 注意： -notrunc已弃用，很快就会被--no-trunc替换。

---

#4楼

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. 如果目标是检查应用程序的日志，则此帖子显示启动tomcat并将日志作为CMD的一部分进行拖尾。 The tomcat log is available on the host using 'docker logs containerid'. 主机上使用“docker logs containerid”可以使用tomcat日志。

http://blog.trifork.com/2013/08/15/using-docker-to-efficiently-create-multiple-tomcat-instances/ http://blog.trifork.com/2013/08/15/using-docker-to-efficiently-create-multiple-tomcat-instances/

---

#5楼

First thing you cannot run 首先，你无法运行

docker run "existing container" command

Because this command is expecting an image and not a container and it would anyway result in a new container being spawned (so not the one you wanted to look at) 因为这个命令期望一个图像而不是一个容器 ，它无论如何都会导致产生一个新的容器（所以不是你想看的那个）

I agree with the fact that with docker we should push ourselves to think in a different way (so you should find ways so that you don't need to log onto the container), but I still find it useful and this is how I work around it. 我同意这样的事实：对于docker我们应该以不同的方式进行思考（所以你应该找到方法让你不需要登录容器），但我仍然觉得它很有用，这就是我工作的方式周围。

I run my commands through supervisor in DEAMON mode. 我在DEAMON模式下通过主管运行我的命令。

Then I execute what I call docker_loop.sh The content is pretty much this: 然后我执行我称之为docker_loop.sh的内容就是这样：

#!/bin/bash
/usr/bin/supervisord
/usr/bin/supervisorctl
while ( true )doecho "Detach with Ctrl-p Ctrl-q. Dropping to shell"sleep 1/bin/bash
done

What it does is that it allows you to "attach" to the container and be presented with the supervisorctl interface to stop/start/restart and check logs. 它的作用是它允许你“附加”到容器并提供supervisorctl接口来停止/启动/重启和检查日志。 If that should not suffice, you can Ctrl+D and you will drop into a shell that will allow you to have a peek around as if it was a normal system. 如果这还不够，你可以Ctrl+D进入一个shell，这样你就可以看到它就像是一个普通的系统一样。

PLEASE DO ALSO TAKE INTO ACCOUNT that this system is not as secure as having the container without a shell, so take all the necessary steps to secure your container. 请注意，该系统不如没有外壳的容器那么安全，因此请采取所有必要步骤来保护容器。

---

#6楼

Just do 做就是了

docker attach container_name

As mentioned in the comments, to detach from the container without stopping it, type Ctrl p then Ctrl q . 如评论中所述，要从容器中分离而不停止它，请键入Ctrl p然后按Ctrl q 。