为什么我的Tutum服务开始,然后在2秒钟内停止与容器状态“死”命令? [英] Why is my Tutum service starting then within 2 seconds stopping with a container status "die" command?
问题描述
从节点31b3f894-a0b9-494e-bca0-9212b642dd15.node接收的事件'死'容器api-1的.dockerapp.io:运行
将容器状态从运行更改为停止
检查触发器
容器没有触发器
我从Docker Cloud(以前的Tutum)支持中得到了一个答案。
当容器内的进程由于任何原因退出时,
然后将该容器视为退出。一旦看到容器不再运行,Docker云就会显示这个
服务为停止。
所以这个特定的容器试图连接到数据库(我没有再次连接),所以它失败了,所以这就是为什么它告诉服务关闭。
I'm running a custom reposository from Docker Hub on Tutum and trying to start a service. I get a Service Start, but then 1-2 seconds, it receives a Container status die command. I can't figure out why.
Received event 'die' from node 31b3f894-a0b9-494e-bca0-9212b642dd15.node.dockerapp.io for container api-1: Running
Changing container state from 'Running' to 'Stopped'
Checking triggers
Container has no triggers
I got an answer back from Docker Cloud (formerly Tutum) support.
When the process started inside a container exits for whatever reason, the container is then considered "exited". Docker cloud shows this service as "stopped" once it sees the container is no longer running.
So this particular container is trying to connect to a database (which I don't have connected again) so it fails, therefore that is why it tells the service to shut down.
这篇关于为什么我的Tutum服务开始,然后在2秒钟内停止与容器状态“死”命令?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!