Docker stop exit code -1 if CMD is default wrapper script

I am creating a tomcat container in Docker with supervisord. If the default command in the Dockerfile is

CMD supervisord -c /etc/supervisord.conf

      

and when i send docker stop command the container exits successfully with exit code 0.

But instead, if I have

CMD ["/run"] 

      

and in run.sh,

supervisord -c /etc/supervisord.conf

      

The dock stop command gives me an exit code of -1. When looking at the logs, it appears that the supervisor has not received a SIGTERM indicating an exit request.

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)

      

unlike previous magazines where it gets sigmmer and exits gracefully.

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)

      

Any help was appreciated.

Thanks, Kartik

UPDATE

supervisord.conf file

[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

      

+3


source to share


1 answer


When you start a process through run.sh, signals are only sent to that process. If you not

  • going out of your way to send signals to child processes eg. with a trap
  • sending signals to a process group.
  • Execution exec supervisord ...

    in run.sh


the child process will not receive signals.

+2


source







All Articles