Description:

When running `make local-dev-up` or `make local-dev-up-with-clair` makefile targets for the first time the containers will spin up but when trying to access the console the browser will display the following error:

The Quay application could not be loaded, which typically indicates an external library could not be loaded (usually due to an ad blocker). Please check the JavaScript console for errors.

This usually occurs when the browser is unable to fetch the compiled Angular Javascript files. Using the tool dive I can see the the JS files are being generated during the Docker build, meaning they are most likely being overwritten during the volume mount of the local directory. The local directory won't contain the build JS files during the first run.

Steps:

1. Follow the local development quickstart guide to ensure the correct tools are installed: https://github.com/quay/quay/blob/master/docs/docker-local-dev.md
2. Ensure the `node_modules` and `static/build` directories haven't been created
3. Run `make local-dev-up` or `make local-dev-up-with-clair` targets
4. Visit `http://localhost:8080` in the console and see the mentioned error

Expected results:

**To view the Quay console in the browser.

Actual results:

Javascript error is rendered in console instead.