Re-adds persistent registry storage to docker compose configuration
Why is this needed
Previous releases of the sandbox (<= v0.5) had persistent storage for the registry, this fixes the regression where registry storage was no longer persistent with v0.6 release and HEAD
How Has This Been Tested?
Bring up a clean environment, verify provisioning works
Push an additional image to the registry that wasn't configured in /registry/registry_images.txt
Do a docker compose down on the provisioner
Do a docker compose up on the provisioner
Verify that all images still exist in the registry
How are existing users impacted? What migration steps/scripts do we need?
This should not impact existing users, since it fixes the regression and issues users would encounter where registry storage is wiped when the registry container is re-created.
Description
Re-adds persistent registry storage to docker compose configuration
Why is this needed
Previous releases of the sandbox (<= v0.5) had persistent storage for the registry, this fixes the regression where registry storage was no longer persistent with v0.6 release and HEAD
How Has This Been Tested?
How are existing users impacted? What migration steps/scripts do we need?
This should not impact existing users, since it fixes the regression and issues users would encounter where registry storage is wiped when the registry container is re-created.