Clean up incorrect and stale docker volumes automatically

[dubbelosix]

#1159 (comment)

So it seems like docker-compose is not re-creating the volumes. This could continue impacting users especially if they switch between demo-rollup in sovereign repo and starter-rollup since both of them use different credentials paths for the volume.

one simple fix is to just have the makefile detect and delete volumes every time (the credentials folder is very light weight. < 1kb)
another approach is to just use different volume names for both

[preston-evans98]

I'd lean toward just deleting the volumes. That way things don't break when someone has two forks of a package

[zvolin]

I'm not sure what is the way to reproduce this, however the credentials persists because the sequencer address is hardcoded

[zvolin]

is there any reproduction from non mac-os? I started to think it's a bug in compose local volume driver specific to this system

[zvolin]

hmm indeed if you have 2 different projects with the same docker layout and volume names, they will never be recreated so you have to either name it differently or delete them on the startup