samurai-dojo-tasks.yml was starting dojo using docker-compose and then again using the systemd service descriptor which seemed to cause issues with provisioning the databases. Removing the ansible tasks which started dojo using docker-compose appears to have fixed the issue.
Additionally commented out the provisioning of Zap proxy as it was failing on my end confounding the root cause of the DB issues. This may need to be a separate issue if it's reproducible.
Reviewer instructions
checkout the dojo_db_conn_fix branch
backup any current versions of samurai (or don't)
run vagrant destroy -f and then vagrant up
Log into the vm as samurai
browse to http://dojo-basic.wtf and http://dojo-scavenger.wtf and make sure the DB seems to be working
If you want to be extra certain run sudo docker exec -it samuraidojo_basicdb_1 /bin/bash then mysql -uroot -psamurai and finally show databases; to see if the database was actually created.
Do the above again but replace samuraidojo_basicdb_1 with samuraidojo_scavengerdb_1
Change Log
samurai-dojo-tasks.ymlwas starting dojo using docker-compose and then again using the systemd service descriptor which seemed to cause issues with provisioning the databases. Removing the ansible tasks which started dojo using docker-compose appears to have fixed the issue.Additionally commented out the provisioning of Zap proxy as it was failing on my end confounding the root cause of the DB issues. This may need to be a separate issue if it's reproducible.
Reviewer instructions
dojo_db_conn_fixbranchvagrant destroy -fand thenvagrant uphttp://dojo-basic.wtfandhttp://dojo-scavenger.wtfand make sure the DB seems to be workingsudo docker exec -it samuraidojo_basicdb_1 /bin/bashthenmysql -uroot -psamuraiand finallyshow databases;to see if the database was actually created.samuraidojo_basicdb_1withsamuraidojo_scavengerdb_1