exit code 143 on graceful shutdown about docker-neo4j

[benbc]

Thanks @gaerfield. That's certainly not expected, we'll take a look.

[benbc]

@gaerfield I've looked into this and I think it's working as expected. Docker stops containers by sending them a SIGTERM. Following standard behaviour Neo4j reports this by exiting with 143. The same thing happens if you issue a docker stop to a container running outside docker-compose (although docker-compose makes it more obvious by logging the exit code).

I'm going to close this now, but please reopen if you think my analysis is wrong.

[gaerfield]

Thanks for the info, this is good to know. I thought, docker stop is going to initiate a "normal" shutdown, which should result in an ExitCode 0. I was wrong here. Thank you for checking.

[spacecowboy]

@gaerfield this will be fixed in 3.2

See related PR: neo4j/neo4j#9108