if you run destroy.sh as the very first command on a bastion host, it’s problematic, since docker doesn’t exist already. We should probably hook into the same logic in desstroy.sh that we do in run.sh to install docker, if not present. Otherwise we get in the messy situation of it running cloudformation delete, then we have to go manually find resources to clean up (since it can use docker/selenium to do stuff in the MC).
Example of the issue:
destroy.sh :: PROJECT_NAME: unity
destroy.sh :: VENUE_NAME: test
./destroy.sh: line 48: NIGHTLY.ENV: No such file or directory
sudo: docker: command not found
Initiating MC AWS Resource Uninstall...
Stopping Selenium docker container...
sudo: docker: command not found
Waiting for Cloudformation Stack Termination..............................[0]
Waiting for Cloudformation Stack Termination..............................[20]
Waiting for Cloudformation Stack Termination..............................[40]
if you run destroy.sh as the very first command on a bastion host, it’s problematic, since docker doesn’t exist already. We should probably hook into the same logic in desstroy.sh that we do in run.sh to install docker, if not present. Otherwise we get in the messy situation of it running cloudformation delete, then we have to go manually find resources to clean up (since it can use docker/selenium to do stuff in the MC).
Example of the issue: