我正在监督下在Docker中构建一个tomcat容器.如果Dockerfile中的默认命令是
CMD supervisord -c /etc/supervisord.conf
当我调度docker stop命令时,容器成功退出,退出代码为0.
但是如果我有
CMD ["/run"]
在run.sh中
supervisord -c /etc/supervisord.conf
docker stop命令为我提供退出代码-1.在查看日志时,主管似乎没有收到指示退出请求的SIGTERM.
2014-10-06 19:48:54,420 CRIT Supervisor running as root (no user in config file)
2014-10-06 19:48:54,450 INFO RPC interface 'supervisor' initialized
2014-10-06 19:48:54,451 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2014-10-06 19:48:54,451 INFO supervisord started with pid 6
2014-10-06 19:48:55,457 INFO spawned: 'tomcat' with pid 9
2014-10-06 19:48:56,503 INFO success: tomcat entered RUNNING state,process has stayed up for > than 1 seconds (startsecs)
与之前的日志相反,在该日志中,它会收到sigterm并正常退出.
2014-10-06 20:02:59,527 CRIT Supervisor running as root (no user in config file)
2014-10-06 20:02:59,556 INFO RPC interface 'supervisor' initialized
2014-10-06 20:02:59,556 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2014-10-06 20:02:59,557 INFO supervisord started with pid 1
2014-10-06 20:03:00,561 INFO spawned: 'tomcat' with pid 9
2014-10-06 20:03:01,602 INFO success: tomcat entered RUNNING state,process has stayed up for > than 1 seconds (startsecs)
2014-10-06 20:05:11,690 WARN received SIGTERM indicating exit request
2014-10-06 20:05:11,690 INFO waiting for tomcat to die
2014-10-06 20:05:12,450 INFO stopped: tomcat (exit status 143)
任何帮助表示赞赏.
谢谢,
卡尔提克
更新:
administratord.conf文件
[supervisord]
nodaemon=true
logfile=/var/log/supervisor/supervisord.log
[program:MysqL]
command=/usr/bin/pidproxy /var/run/MysqLd/MysqLd.pid /usr/bin/MysqLd_safe --pid-file=/var/run/MysqLd/MysqLd.pid
stdout_logfile=/tmp/MysqL.log
stderr_logfile=/tmp/MysqL_err.log
[supervisorctl]
serverurl=unix:///tmp/supervisor.sock
[unix_http_server]
file=/tmp/supervisor.sock ; path to your socket file
[rpcinterface:supervisor]
supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface
最佳答案
通过run.sh运行该进程时,信号仅发送到该进程.除非你是
原文链接:https://www.f2er.com/docker/532542.html>尽力向子进程发送信号,例如带陷阱
>将信号发送到过程组.
>在exec.sh中执行exec主管…
子进程将无法获得信号.