[英]Why is my Tutum service starting then within 2 seconds stopping with a container status “die” command?
I'm running a custom reposository from Docker Hub on Tutum and trying to start a service. 我正在从Tutum上的Docker Hub运行自定义存储库,并尝试启动服务。 I get a Service Start, but then 1-2 seconds, it receives a Container status die command. 我得到一个服务启动,但是然后在1-2秒后,它收到一个Container status die命令。 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. 我从Docker Cloud(以前称为Tutum)的支持中得到了答案。
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. 一旦发现容器不再运行,Docker云会将其显示为“已停止”。
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. 因此,此特定容器正在尝试连接到数据库(我没有再连接),因此它失败了,因此这就是为什么它告诉服务关闭的原因。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.