When I issue
docker stop <id>, the process doesn't exit cleanly and
bitcoind has to roll-forward blocks on the next startup.
018-03-04 04:15:25 Rolling forward 0000000000000000001728efc81b210835048a7321ba3ec93197f698fac080ab (511863) 2018-03-04 04:15:26 Rolling forward 0000000000000000002be2e2792facd65e2358f874bc48f6410b80ecc8a6e756 (511864) 2018-03-04 04:15:26 Rolling forward 0000000000000000004740c4832b47a1c852db87cf4b9aea559db8712d2971a5 (511865)
This seems to be an issue with the
dbcache not being written to disk prior to exit. I'm not sure if it's issuing a SIGTERM and then SIGKILL.
What is the best way to stop bitcoind to prevent any database related issues?