Devstack volumes are not reliably destroyed
timmc-edx opened this issue · 6 comments
make dev.destroy does not seem to always destroy all of the Docker volumes. After running it, I have sometimes seen the output of docker volume ls include some volume names starting with devstack_. This might account for some oddities around mysql80.
Haven't been able to reproduce this again, though.
(Ticket previously incorrectly stated that there was no way command that deleted the volumes, but this was incorrect.)
You know what? I was wrong, it totally does do this. destroy.sh runs docker-compose down -v and that -v refers to volumes. Maybe I ran the wrong command!
But... interestingly, make dev.destroy doesn't remove all of the devstack_* volumes. Or, not always?
Possible cause: down -v may only remove volumes for running containers and leave the others in place.
Blocked pending more investigation by @timmc-edx
Hmm, I tried running make dev.destroy while only mysql80 was running, but it correctly removed all of the other devstack_* volumes as well.
We should document "look at docker volume ls" as a last-ditch troubleshooting step and then close this.