blocks|key|2914229|text|这个问题是因为如果容器中没有正在运行的应用程序，那么docker容器就会退出。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2914230|-d+|code-block|syntax|javascript|2914231|选项就是在守护模式下运行一个容器。|2914232|因此，让您容器持续运行的诀窍是指向docker中的一个外壳文件，该文件将使您的应用程序running.You可以尝试使用start.sh文件|2914233|Eg:+docker+run+-d+centos+sh+/yourlocation/start.sh|2914234|这个start.sh应该指向一个永不结束的应用程序。|2914235|如果您不想让任何应用程序运行，您可以安装monit，它将使您的停靠容器保持运行。请让我们知道这两个案例是否适用于您保持您的容器运行。|offset|length|style|CODE|2914236|万事如意|2914237|entityMap^0|0|0|0|0|0|0|K|5|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|12|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|14|8|@$Q|15|R|16|S|T]]|9|@]|A|$]]|$1|U|3|V|5|6|7|17|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

Hi this issue is because docker containers exit if there is no running application in the container.

<pre><code>-d 
</code></pre>

option is just to run a container in deamon mode.

So the trick to make your container continuously running is point to a shell file in docker which will keep your application running.You can try with a start.sh file

<pre><code>Eg: docker run -d centos sh /yourlocation/start.sh
</code></pre>

This start.sh should point to a never ending application.

In case if you dont want any application to be running,you can install <code>monit</code> which will keep your docker container running.
Please let us know if these two cases worked for you to keep your container running.

All the best

blocks|key|133710|text|Docker需要你的命令保持在前台运行。否则，它会认为您的应用程序会停止并关闭容器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|133711|因此，如果您的docker入口脚本是一个后台进程，如下所示：|133712|/usr/local/bin/confd+-interval=30+-backend+etcd+-node+$CONFIG_CENTER+&|code-block|syntax|javascript|133713|如果以后没有其他前台进程触发，'&‘会使容器停止并退出。所以解决方案就是去掉'&‘或者在它之后运行另一个前台CMD，比如|133714|tail+-f+server.log|133715|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|$]]

Docker requires your command to keep running in the foreground. Otherwise, it thinks that your applications stops and shutdown the container.

So if your docker entry script is a background process like following:

<pre><code>/usr/local/bin/confd -interval=30 -backend etcd -node $CONFIG_CENTER &amp;
</code></pre>

The '&amp;' makes the container stop and exit if there are no other foreground process triggered later. 
So the solution is just remove the '&amp;' or have another foreground CMD running after it, such as

<pre><code>tail -f server.log
</code></pre>

blocks|key|133717|text|根据this+answer的说法，添加-t标志将阻止容器在后台运行时退出。然后，您可以使用docker+exec+-i+-t+<image>+/bin/bash进入shell提示符。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|133718|docker+run+-t+-d+<image>+<command>|code-block|syntax|javascript|133719|看起来-t选项isn't+documented+very+well，尽管帮助中说它“分配了一个伪TTY”。|133720|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/36872226/2104168|1|https://stackoverflow.com/a/32110513/2104168^0|J|2|19|Z|2|B|0|0|0|7|Q|1|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@$9|11|A|12|1|13]]|E|$]]|$1|F|3|G|5|H|7|14|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|15|8|@]|D|@$9|16|A|17|1|18]]|E|$]]|$1|M|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]|U|$5|P|Q|R|E|$S|V]]]]

According to <a href="https://stackoverflow.com/a/36872226/2104168">this answer</a>, adding the <code>-t</code> flag will prevent the container from exiting when running in the background. You can then use <code>docker exec -i -t &lt;image&gt; /bin/bash</code> to get into a shell prompt.

<pre><code>docker run -t -d &lt;image&gt; &lt;command&gt;
</code></pre>

It seems that the -t option <a href="https://stackoverflow.com/a/32110513/2104168">isn't documented very well</a>, though the help says that it "allocates a pseudo-TTY."

blocks|key|133793|text|也许只有我，但在CentOS+7.3.1611和Docker1.12.6上，我最终不得不使用@VonC+&+@Christopher+Simon发布的答案的组合来让它可靠地工作。在此之前，我所做的任何事情都不会阻止容器在成功运行CMD后退出。我正在启动oracle-xe-11Gr2和sshd。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|133794|Dockerfile|133795|...
RUN+ssh-keygen+-t+rsa+-f+/etc/ssh/ssh_host_rsa_key+-N+''+&&+systemctl+enable+sshd
...
CMD+/etc/init.d/oracle-xe+start+&&+/sbin/sshd+&&+tail+-f+/dev/null|code-block|syntax|javascript|133796|然后添加-d+-t和-i以运行|133797|docker+run+--shm-size=2g+--name+oracle-db+-d+-t+-i+-p+5022:22+-p+5080:8080+-p+1521:1521+centos-oracle:7.3.1611+|133798|几个小时后我的头终于撞到了墙上|133799|ssh+-v+root@127.0.0.1+-p+5022
...
root@127.0.0.1's+password:+
debug1:+Authentication+succeeded+(password).|133800|无论出于何种原因，如果删除了尾部-f，或者省略了任何-t+-d+-i选项，上述代码将在执行CMD后退出。|133801|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

Maybe it is just me but on CentOS 7.3.1611 and Docker 1.12.6 but I ended up having to use a combination of the answers posted by @VonC &amp; @Christopher Simon to get this working reliably. Nothing I did before this would stop the container from exiting after it ran CMD successfully. I am starting oracle-xe-11Gr2 and sshd.

Dockerfile

<pre><code>...
RUN ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key -N '' &amp;&amp; systemctl enable sshd
...
CMD /etc/init.d/oracle-xe start &amp;&amp; /sbin/sshd &amp;&amp; tail -f /dev/null
</code></pre>

Then adding -d -t and -i to run

<pre><code>docker run --shm-size=2g --name oracle-db -d -t -i -p 5022:22 -p 5080:8080 -p 1521:1521 centos-oracle:7.3.1611 
</code></pre>

Finally after hours of bashing my head against the wall

<pre><code>ssh -v root@127.0.0.1 -p 5022
...
root@127.0.0.1's password: 
debug1: Authentication succeeded (password).
</code></pre>

For whatever reason the above will exit after executing CMD if the tail -f is removed, or any of the -t -d -i options are omitted.

blocks|key|134968|text|执行命令，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|134969|docker+run+-t+-d+<image-name>|code-block|syntax|javascript|134970|如果您想要指定端口，则使用如下命令：|134971|docker+run+-t+-d+-p+<port-no>+<image-name>|134972|使用以下命令验证正在运行的容器：|134973|docker+ps|134974|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|$]]

execute command as follows :

<pre><code>docker run -t -d &lt;image-name&gt;
</code></pre>

if you want to specify port then command as below:

<pre><code>docker run -t -d -p &lt;port-no&gt; &lt;image-name&gt;
</code></pre>

verify the running container using following command:

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

blocks|key|2914496|text|您可以使用以下任一方法来完成您想要的任务：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2914497|docker+run+-t+-d+<image-name>|code-block|syntax|javascript|2914498|或|2914499|docker+run+-i+-d+<image-name>|2914500|2914501|docker+run+-it+-d+<image-name>|2914502|其他答案中建议的命令参数(即尾部-f+/dev/null)是完全可选的，并且不需要让容器保持在后台运行。|2914503|还要注意Docker文档表明，组合-i和-t选项将使其行为类似于shell。|2914504|请参见：|2914505|https://docs.docker.com/engine/reference/run/#foreground|offset|length|2914506|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|0|0|0|0|0|1K|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|16|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|17|8|@]|9|@]|A|$E|F]]|$1|K|3|H|5|6|7|18|8|@]|9|@]|A|$]]|$1|L|3|M|5|D|7|19|8|@]|9|@]|A|$E|F]]|$1|N|3|O|5|6|7|1A|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1B|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1C|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1D|8|@]|9|@$V|1E|W|1F|1|1G]]|A|$]]|$1|X|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|Y|$Z|$5|10|11|12|A|$13|U]]]]

You can accomplish what you want with either:

<pre><code>docker run -t -d &lt;image-name&gt;
</code></pre>

or

<pre><code>docker run -i -d &lt;image-name&gt;
</code></pre>

or

<pre><code>docker run -it -d &lt;image-name&gt;
</code></pre>

The command parameter as suggested by other answers (i.e. tail -f /dev/null) is completely optional, and is NOT required to get your container to stay running in the background. 

Also note the Docker documentation suggests that combining -i and -t options will cause it to behave like a shell.

See:

<a href="https://docs.docker.com/engine/reference/run/#foreground" rel="noreferrer">https://docs.docker.com/engine/reference/run/#foreground</a>

blocks|key|2914554|text|背景|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2914555|Docker容器运行一个进程(“命令”或“入口点”)，使其保持活动状态。只要命令继续运行，容器就会继续运行。|2914556|在您的示例中，命令(默认情况下是centos:latest上的bash+)会立即退出(就像bash在没有连接到终端并且没有什么可运行时一样)。|offset|length|style|CODE|2914557|通常，当您在守护程序模式下运行容器(使用-d)时，容器会运行某种守护程序进程(如httpd)。在这种情况下，只要httpd守护进程正在运行，容器就会保持活动状态。|2914558|您似乎想要做的是在容器内部没有运行守护进程的情况下保持容器的活动状态。这有点奇怪(因为在您与容器交互之前，容器不会做任何有用的事情，可能是与docker+exec交互)，但在某些情况下，这样做可能是有意义的。|2914559|(您的意思是到达容器内的bash提示符吗？这很简单！docker+run+-it+centos:latest)|2914560|解决方案|2914561|让容器无限期地处于守护进程模式下的一种简单方法是作为容器的命令运行sleep+infinity。这并不依赖于做一些奇怪的事情，比如在守护模式下分配一个TTY。尽管它确实依赖于做一些奇怪的事情，比如使用sleep作为主要命令。|2914562|$+docker+run+-d+centos:latest+sleep+infinity
$+docker+ps
CONTAINER+ID++IMAGE+++++++++COMMAND++++++++++CREATED+++++++STATUS+++++++PORTS+NAMES
d651c7a9e0ad++centos:latest+"sleep+infinity"+2+seconds+ago+Up+2+seconds+++++++nervous_visvesvaraya|code-block|syntax|javascript|2914563|替代解决方案|2914564|正如cjsimon所指出的，-t选项分配一个“伪tty”。这会导致它继续无限期地运行，因为它认为它连接到一个交互式的TTY+(即使如果你不通过-i就无法与那个特定的TTY进行交互)。无论如何，下面的代码也应该能起到作用：|2914565|$+docker+run+-t+-d+centos:latest|2914566|不能100%25确定-t是否会产生其他奇怪的交互；如果会，请在下面留下评论。|2914567|entityMap^0|0|0|G|D|0|K|2|14|5|0|1Y|B|0|Q|S|0|0|X|E|2S|5|0|0|0|E|2|1Z|2|0|0|8|2|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1A|8|@$F|1B|G|1C|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1D|8|@$F|1E|G|1F|H|I]|$F|1G|G|1H|H|I]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1I|8|@$F|1J|G|1K|H|I]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1L|8|@$F|1M|G|1N|H|I]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1O|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1P|8|@$F|1Q|G|1R|H|I]|$F|1S|G|1T|H|I]]|9|@]|A|$]]|$1|T|3|U|5|V|7|1U|8|@]|9|@]|A|$W|X]]|$1|Y|3|Z|5|6|7|1V|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1W|8|@$F|1X|G|1Y|H|I]|$F|1Z|G|20|H|I]]|9|@]|A|$]]|$1|12|3|13|5|V|7|21|8|@]|9|@]|A|$W|X]]|$1|14|3|15|5|6|7|22|8|@$F|23|G|24|H|I]]|9|@]|A|$]]|$1|16|3|-4|5|6|7|25|8|@]|9|@]|A|$]]]|17|$]]

<h2>Background</h2>

A Docker container runs a process (the "command" or "entrypoint") that keeps it alive. The container will continue to run as long as the command continues to run.

In your case, the command (<code>/bin/bash</code>, by default, on <code>centos:latest</code>) is exiting immediately (as bash does when it's not connected to a terminal and has nothing to run).

Normally, when you run a container in daemon mode (with <code>-d</code>), the container is running some sort of daemon process (like <code>httpd</code>). In this case, as long as the httpd daemon is running, the container will remain alive.

What you appear to be trying to do is to keep the container alive without a daemon process running inside the container. This is somewhat strange (because the container isn't doing anything useful until you interact with it, perhaps with <code>docker exec</code>), but there are certain cases where it might make sense to do something like this.

(Did you mean to get to a bash prompt inside the container? That's easy! <code>docker run -it centos:latest</code>)

<h2>Solution</h2>

A simple way to keep a container alive in daemon mode indefinitely is to run <code>sleep infinity</code> as the container's command. This does not rely doing strange things like allocating a TTY in daemon mode. Although it does rely on doing strange things like using <code>sleep</code> as your primary command.

<pre><code>$ docker run -d centos:latest sleep infinity
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
d651c7a9e0ad centos:latest "sleep infinity" 2 seconds ago Up 2 seconds nervous_visvesvaraya
</code></pre>

<h2>Alternative Solution</h2>

As indicated by cjsimon, the <code>-t</code> option allocates a "pseudo-tty". This tricks bash into continuing to run indefinitely because it thinks it is connected to an interactive TTY (even though you have no way to interact with that particular TTY if you don't pass <code>-i</code>). Anyway, this should do the trick too:

<pre><code>$ docker run -t -d centos:latest
</code></pre>

Not 100% sure whether <code>-t</code> will produce other weird interactions; maybe leave a comment below if it does.

blocks|key|136833|text|我已经在下面有同样问题的帖子中解释了这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|136834|How+to+retain+docker+alpine+container+after+"exit"+is+used?|offset|length|136835|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/45638784/how-to-retain-docker-alpine-container-after-exit-is-used/51133128#51133128^0|0|0|1N|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

I have explained it in the following post that has the same question.

<a href="https://stackoverflow.com/questions/45638784/how-to-retain-docker-alpine-container-after-exit-is-used/51133128#51133128">How to retain docker alpine container after &quot;exit&quot; is used?</a>

blocks|key|2914744|text|参数顺序很重要|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2914745|Jersey+Beans答案(所有3个例子)对我有效。经过相当多的尝试和错误之后，我意识到参数的顺序很重要。|2914746|保持容器在后台运行：docker+run+-t+-d+<image-name>|offset|length|style|CODE|2914747|保持容器在前台运行：docker+run+<image-name>+-t+-d|2914748|这对我来说并不明显，因为我有Powershell的背景。|2914749|entityMap^0|0|0|A|T|0|A|T|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@$F|S|G|T|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@$F|V|G|W|H|I]]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|O|$]]

Argument order matters

Jersey Beans answer (all 3 examples) worked for me. After quite a bit of trial and error I realized that the order of the arguments matter. 

Keeps the container running in the background:
 <code>docker run -t -d &lt;image-name&gt;</code>

Keeps the container running in the foreground: <code>docker run &lt;image-name&gt; -t -d</code>

It wasn't obvious to me coming from a Powershell background.

blocks|key|135104|text|我在docker文件中从ENTRYPOINT运行以下代码片段：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|135105|while+true
do
++++echo+"Press+[CTRL%2BC]+to+stop.."
++++sleep+1
done|code-block|syntax|javascript|135106|运行构建好的docker镜像：|135107|docker+run+-td+<image+name>|135108|登录容器shell：|135109|docker+exec+-it+<container+id>+/bin/bash|135110|entityMap^0|C|A|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|10|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|S|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|T|$]]

I have this code snippet run from the <code>ENTRYPOINT</code> in my docker file:

<pre><code>while true
do
 echo "Press [CTRL+C] to stop.."
 sleep 1
done
</code></pre>

Run the built docker image as:

<pre><code>docker run -td &lt;image name&gt;
</code></pre>

Log in to the container shell:

<pre><code>docker exec -it &lt;container id&gt; /bin/bash
</code></pre>

blocks|key|2702420|text|我也有同样的问题，只是打开另一个终端，并对其进行狂欢，这对我来说是有效的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2702421|创建容器：|2702422|docker+run+-d+mcr.microsoft.com/mssql/server:2019-CTP3.0-ubuntu
containerid=52bbc9b30557|code-block|syntax|javascript|2702423|起始容器：|2702424|docker+start+52bbc9b30557|2702425|启动bash以保持容器运行：|2702426|docker+exec+-it+52bbc9b30557+bash|2702427|启动您需要的流程：|2702428|docker+exec+-it+52bbc9b30557+/path_to_cool_your_app|2702429|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

I had the same issue, just opening another terminal with a bash on it worked for me :

create container: 

<pre><code>docker run -d mcr.microsoft.com/mssql/server:2019-CTP3.0-ubuntu
containerid=52bbc9b30557
</code></pre>

start container:

<pre><code>docker start 52bbc9b30557
</code></pre>

start bash to keep container running:

<pre><code>docker exec -it 52bbc9b30557 bash
</code></pre>

start process you need:

<pre><code>docker exec -it 52bbc9b30557 /path_to_cool_your_app
</code></pre>

blocks|key|136371|text|如果您在Dockerfile的末尾使用CMD，那么可以做的就是在末尾添加代码。只有当你的docker是建立在ubuntu或任何可以使用bash的操作系统上时，这才能起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|136372|&&+/bin/bash|code-block|syntax|javascript|136373|简单地说，Dockerfile的末尾将如下所示。|136374|...

CMD+ls+&&+...+&&+/bin/bash|136375|因此，如果您在运行docker镜像后有任何东西自动运行，并且当任务完成时，bash终端将在您的docker中处于活动状态。因此，您可以输入shell命令。|136376|entityMap^0|0|0|0|0|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|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

If you are using CMD at the end of your Dockerfile, what you can do is adding the code at the end. This will only work if your docker is built on ubuntu, or any OS that can use bash. 

<pre><code>&amp;&amp; /bin/bash
</code></pre>

Briefly the end of your Dockerfile will look like something like this.

<pre><code>...

CMD ls &amp;&amp; ... &amp;&amp; /bin/bash
</code></pre>

So if you have anything running automatically after you run your docker image, and when the task is complete the bash terminal will be active inside your docker. Thereby, you can enter you shell commands.

blocks|key|136915|text|Docker容器如果里面的任务完成就会退出，所以如果你想让它保持存活，即使它没有任何任务或者已经完成了它们，你可以执行docker+run+-di+image。在执行docker+container+ls之后，您将看到它正在运行。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|136916|entityMap^0|1N|K|2B|J|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Docker container exits if task inside is done, so if you want to keep it alive even if it does not have any job or already finished them, you can do <code>docker run -di image</code>. After you do <code>docker container ls</code> you will see it running.

blocks|key|134023|text|如果您想要对容器进行操作，您需要在前台运行它以保持其存活。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|134024|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

if you want to operate on the container, you need to run it in foreground to keep it alive.

blocks|key|2915083|text|在交互模式下运行docker可能会解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2915084|以下是在交互模式下和不在交互模式下运行图像的示例|2915085|chaitra@RSK-IND-BLR-L06:~/dockers$+sudo+docker+run+-d+-t+-i+test_again1.0|offset|length|style|BOLD|2915086|chaitra@RSK-IND-BLR-L06:~/dockers$+sudo+docker+ps|2915087|容器ID映像命令已创建状态端口名称|2915088|chaitra@RSK-IND-BLR-L06:~/dockers$+sudo+docker运行c3d6a9529fd70c5b2dc2d7e90fe662d19c6dad8549e9c812fb2b7ce2105d7ff5+-d+-t+-i+test_again1.0+bash+docker|2915089|chaitra@RSK-IND-BLR-L06:~/dockers$+sudo+docker+ps|2915090|CONTAINER+ID+IMAGE命令CREATED+STATUS+PORTS+NAMES+c3d6a9529fd7+test_again1.0+"bash“2秒前Up+1秒awesome_haibt|2915091|entityMap^0|0|0|0|21|0|0|1D|0|0|0|3W|0|0|1D|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@$F|Y|G|Z|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@$F|11|G|12|H|I]]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|14|8|@$F|15|G|16|H|I]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|17|8|@$F|18|G|19|H|I]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1A|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|U|$]]

Running docker with interactive mode might solve the issue.

Here is the example for running image with and without interactive mode

chaitra@RSK-IND-BLR-L06:~/dockers$ sudo docker run -d -t -i test_again1.0
b6b9a942a79b1243bada59db19c7999cfff52d0a8744542fa843c95354966a18

chaitra@RSK-IND-BLR-L06:~/dockers$ sudo docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

chaitra@RSK-IND-BLR-L06:~/dockers$ sudo docker run -d -t -i test_again1.0 bash
c3d6a9529fd70c5b2dc2d7e90fe662d19c6dad8549e9c812fb2b7ce2105d7ff5

chaitra@RSK-IND-BLR-L06:~/dockers$ sudo docker ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c3d6a9529fd7 test_again1.0 "bash" 2 seconds ago Up 1 second awesome_haibt

blocks|key|2702628|text|我也面临着同样的问题，但方式不同。当我创建码头容器时。它会自动停止正在后台运行的未使用的容器。有时，它还会停止正在使用的容器。在我的情况下，这是因为它之前拥有的docker.sock文件的权限。你要做的是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2702629|当我在|2702630|上工作时，我是从here)|ordered-list-item|offset|length|2702631|安装的。|2702632|2702633|运行命令以更改权限。|2702634|2702635|sudo+chmod+666+/var/run/docker.sock|style|CODE|2702636|2702637|安装docker-compose+(这是可选的，因为我有一个组合文件来一起创建许多容器)|2702638|2702639|sudo+curl+-L+"https://github.com/docker/compose/releases/download/1.26.0/docker-compose-$(uname+-s)-$(uname+-m)"+-o+/usr/local/bin/docker-compose|2702640|sudo+chmod+%2Bx+/usr/local/bin/docker-compose|2702641|对版本进行|2702642|检查，以确保我的版本是最新的，并且某些deprications.|2702643|不会出现问题|2702644|2702645|，然后运行docker容器构建。|2702646|2702647|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/engine/install/ubuntu/^0|0|0|8|4|0|0|0|0|0|0|0|Z|0|0|0|0|0|41|0|0|17|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1J|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1K|8|@]|9|@$G|1L|H|1M|1|1N]]|A|$]]|$1|I|3|J|5|6|7|1O|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|L|3|M|5|F|7|1Q|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1S|8|@$G|1T|H|1U|Q|R]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]|$1|T|3|U|5|F|7|1W|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1Y|8|@$G|1Z|H|20|Q|R]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|21|8|@$G|22|H|23|Q|R]]|9|@]|A|$]]|$1|10|3|11|5|6|7|24|8|@]|9|@]|A|$]]|$1|12|3|13|5|F|7|25|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|26|8|@]|9|@]|A|$]]|$1|16|3|-4|5|6|7|27|8|@]|9|@]|A|$]]|$1|17|3|18|5|F|7|28|8|@]|9|@]|A|$]]|$1|19|3|-4|5|6|7|29|8|@]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|2A|8|@]|9|@]|A|$]]]|1B|$1C|$5|1D|1E|1F|A|$1G|1H]]]]

I was also facing the same problem but in a different manner. When I create the docker containers. it automatically stops the unused containers which are just running in the background. Sometimes it also stops the containers that are in the use.
In my situation, this is because of the permission of the docker.sock files it earlier has.
what you have to do is :-
<ol>
<li>Install docker again.(As i work on ubuntu i install it from <a href="https://docs.docker.com/engine/install/ubuntu/" rel="nofollow noreferrer">here</a>)
</li>
<li>Run the command to change the permissions.
<code>sudo chmod 666 /var/run/docker.sock</code>
</li>
<li>Install docker-compose (this is optional as I have compose file to create many containers together)
<code>sudo curl -L &quot;https://github.com/docker/compose/releases/download/1.26.0/docker-compose-$(uname -s)-$(uname -m)&quot; -o /usr/local/bin/docker-compose</code>
<code>sudo chmod +x /usr/local/bin/docker-compose</code>
</li>
<li>check for the version to ensure that I have the latest one and not get problem with some deprications.
</li>
<li>Then I run the docker container build.
</li>
</ol>

blocks|key|2702660|text|这4个命令都可以让您的docker容器保持运行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2702661|docker+run+-td+centos|code-block|syntax|javascript|2702662|docker+run+-dt+centos|2702663|docker+run+-t+-d+centos|2702664|docker+run+-d+-t+centos|2702665|entityMap^0|0|0|0|0|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|D|7|Q|8|@]|9|@]|A|$E|F]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|D|7|S|8|@]|9|@]|A|$E|F]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

These 4 commands all work to keep your docker container running:
<pre><code>docker run -td centos
</code></pre>
<pre><code>docker run -dt centos
</code></pre>
<pre><code>docker run -t -d centos
</code></pre>
<pre><code>docker run -d -t centos
</code></pre>

blocks|key|137031|text|在前台/分离状态下运行容器有多种选择。但是如果您仍然觉得问题没有解决，您可以尝试通过查看日志来排除故障。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|137032|sudo+docker+logs+-f+>>+container.log|137033|此外，您还可以使用--details来显示提供给日志的额外详细信息。|137034|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

There are multiple options out there to run the container in foreground/detached state. But if you still feel the issue is not resolved, you can try troubleshooting the issue by viewing the logs.
sudo docker logs -f &gt;&gt; container.log
additionally you can also use --details to show extra details provided to logs.

blocks|key|135216|text|您可以简单地使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|135217|docker+container+run+-d+-it+<container+name+or+id>+/bin/bash|code-block|syntax|javascript|135218|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 simply use:
<pre><code>docker container run -d -it &lt;container name or id&gt; /bin/bash
</code></pre>

According to tutorial I read so far, use "<code>docker run -d</code>" will start a container from image, and the container will run in background. This is how it looks like, we can see we already have container id.

<pre><code>root@docker:/home/root# docker run -d centos
605e3928cdddb844526bab691af51d0c9262e0a1fc3d41de3f59be1a58e1bd1d
</code></pre>

But if I ran "<code>docker ps</code>", nothing was returned.

So I tried "<code>docker ps -a</code>", I can see container already exited:

<pre><code>root@docker:/home/root# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
605e3928cddd centos:latest "/bin/bash" 31 minutes ago Exited (0) 31 minutes ago kickass_swartz
</code></pre>

Anything I did wrong? How can I troubleshoot this issue?

Docker container will automatically stop after "docker run -d"

容器

Docker

CentOS

根据我到目前为止读过的教程，使用"docker run -d“将从图像启动一个容器，该容器将在后台运行。这是它看起来的样子，我们可以看到我们已经有了容器id。root@docker:/home/root# docker run -d centos605e3928cdddb844526bab691af51d0c9262e...

问Docker容器在docker run -d后会自动停止
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Docker容器在docker run -d后会自动停止EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Docker容器在docker run -d后会自动停止
EN