Commit c56fc47
committed
use 'docker stop' instead of 'docker kill'
The 'stop' command first tries SIGTERM before resorting to SIGKILL,
which is a gentler way to stop processes. (SIGTERM gives processes an
opportunity to clean up before exiting; SIGKILL can't be caught so it
is very abrupt.)1 parent 2609cbb commit c56fc47
1 file changed
Lines changed: 2 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -55,8 +55,8 @@ CONFIG=/tmp/python-gitlab.cfg | |||
| 55 | 55 | ||
| 56 | 56 | cleanup() { | |
| 57 | 57 | rm -f "${CONFIG}" | |
| 58 | - log "Killing gitlab-test docker container..." | ||
| 59 | - docker kill gitlab-test >/dev/null 2>&1 | ||
| 58 | + log "Stopping gitlab-test docker container..." | ||
| 59 | + docker stop gitlab-test >/dev/null 2>&1 | ||
| 60 | 60 | log "Removing gitlab-test docker container..." | |
| 61 | 61 | docker rm gitlab-test >/dev/null 2>&1 | |
| 62 | 62 | log "Deactivating Python virtualenv..." | |
0 commit comments