Stop and Start an existing sedex-Client Docker Container

A sedex-Client container can be stopped and started like any other Docker container.

Stop the sedex-Client container

Stop the sedex-Client container as follows (adapt the name of the container to your configuration):

$ docker stop sedex-client

Info

Stopping a sedex-Client container can take up to 65 seconds. This allows the sedex-Client to gracefully shut down and clean up temporary data. Make sure that Docker or your orchestration platform waits long enough before killing the container (see option --stop-timeout in Create and Run).

The exit code of the stopped container shows whether the sedex-Client has been shut down properly: 0 means a graceful shutdown, any other exit code means that the sedex-Client was terminated or has failed. In this case, check the log files: if the sedex-Client did not stop within 60 seconds, the container log contains the message Shutdown not graceful. The exit code 137 means that the container was killed, e.g. because the stop timeout was too short or the container ran out of memory.

Start the sedex-Client container

Start the sedex-Client container as follows (adapt the name of the container to your configuration):

$ docker start sedex-client