Docker containers generate insecure config

[rquarry]

Describe the bug
In the Installing CALDERA section of the docs:

• Following the "concise" installation instructions for a host based install results in secure configuration values in conf/local.yml.
• Building via the "Docker Deployment" section of the installation guide results in containers that have default config values for API tokens, user passwords, etc.
• Issue is due to line 25 in the Dockerfile that pre-creates local.yml, which causes app/utility/config_generator.py to skip creating secure config values when server.py is run.

To Reproduce
Steps to reproduce the behavior:

1. Follow build documentation for "Docker Deployment"
2. Observe contents of conf/local.yml: docker exec -it [Container ID] cat conf/local.yml
3. Comment out line 25 of Dockerfile, re-build/run container.
4. Observe conents of conf/local.yml

Expected behavior
local.yml should contain unique values upon execution of server.py. This is especially true for containers that may have multiple instances.

Screenshots
User results after standard Docker container build and run:

User results after commenting out line 25 of Dockerfile and rebuilding container:

Desktop (please complete the following information):

• OS: Fedora 37
• Browser: Firefox
• Version: 4.1.0

I am happy to submit a PR for this, but wasn't sure what to do about disabling the Atomic plugin in the Dockerfile. Perhaps it should be removed from the default config?

[github-actions]

Looks like your first issue -- we aim to respond to issues as quickly as possible. In the meantime, check out our documentation here: http://caldera.readthedocs.io/

[github-actions]

This issue is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 5 days

[github-actions]

This issue is stale because it has been open 20 days with no activity. Remove stale label or comment or this will be closed in 5 days