restart failed containers about kontena HOT 4 CLOSED

Yes we support automatic restart of failed containers. If you issue stop command, docker does not translate that to failure because you (as an administrator) issued a stop. If container fails without interaction then it's restarted automatically.

You can try it out by killing the process on node1.

from kontena.

I tried again with docker kill ghost-blog-1, but the service does not get restarted.

docker kill should send SIGKILL to the process, as shown here:

$ docker kill --help

Usage: docker kill [OPTIONS] CONTAINER [CONTAINER...]

Kill a running container using SIGKILL or a specified signal

  --help=false         Print usage
  -s, --signal=KILL    Signal to send to the container

Again, container status is stopped and service status is running.

from kontena.

Yes, this is expected behaviour. Try again so that you find pid and just kill it directly from host without docker tooling, sudo kill -9 <pid> .

from kontena.

Ok, if I get the pid of the container with docker inspect --format '{{.State.Pid}}, {{.ID}}' ghost-blog-1 and then kill this process with kill -9 <pid>, the process gets restarted. Thanks for your support!

from kontena.