[
https://issues.apache.org/jira/browse/IGNITE-8932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16533103#comment-16533103
]
Ivan Yani edited comment on IGNITE-8932 at 7/4/18 11:16 PM:
------------------------------------------------------------
How to reproduce:
docker run --name ignite
[apacheignite|https://hub.docker.com/u/apacheignite/]/ignite:2.5.0
docker stop ignite
docker ps |grep ignite
Exited (137)
So exit code is 137 which means process didn't respond to SIGTERM and was killed
was (Author: vanuan):
How to reproduce:
docker run --name ignite
[apacheignite|https://hub.docker.com/u/apacheignite/]/[ignite|https://hub.docker.com/r/apacheignite/ignite/]:2.5.0
docker stop ignite
docker ps |grep ignite
Exited (137)
So exit code is 137 which means process didn't respond to SIGTERM and was killed
> Docker image: doesn't handle SIGTERM
> ------------------------------------
>
> Key: IGNITE-8932
> URL: https://issues.apache.org/jira/browse/IGNITE-8932
> Project: Ignite
> Issue Type: Bug
> Reporter: Ivan Yani
> Priority: Major
>
> So there's this "pid 1" issue with ignite image published on docker hub. The
> problem manifests in not being able to send SIGTERM to ignite java process.
> The reason of this issue is that the signal is sent to the shell script which
> start ignite, not ignite itself. To fix the issue you need to use "exec" in
> bash script to replace bash process with java process.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
