Blaze volume survives execution of resetBlaze.sh

[Malekoko]

Hi folks,

the execution of resetBlaze.sh does not reset the Blaze volume on our site. Can somebody confirm? Blaze version is 0.14.

[DiCanio]

Hi @Malekoko,

just tried to reproduce this without success. When running resetBlaze.sh any volume associated with Blaze gets deleted. The subsequent restart of Blaze, which the script also takes care of, creates a new volume leaving Blaze without any existing data.

Please note, that this has been tested in isolation, only starting Blaze and resetting it without any other components running.

If not running a heavily altered version of this project then you should be able to confirm whether the volume got recreated by running:

docker volume inspect codex-deploy_blaze-data | jq -r '.[0].CreatedAt'

This yields the volume's creation time which should be somewhere near the time resetBlaze.sh has been invoked.

Please verify the above. Should creation times do not align then drop us a message here and we'll dig a bit deeper.

[Malekoko]

The output does not mention to remove the volume. I'm using the abide deployment right now. The inspect command from above tells me the volume is from 5th of january.