Need your con-mms.properties to be prepared and mounted as a separate volume.
Passing in configs using --env didn't work as the .properties file is not parsed using bash and the variable substitution does not work. So for now using your own file in a volume is the way to go. Anything that is referenced in this file such as key file sand pems should all be stored locally and then mounted as necessary.
So for now provide your own gen.key....and conf-mms.properties
Other things need to be worked out as well... such as the gen.key issue with new containers you might kick off
Lastly there is the issue that mms-mongodb is not the executable that maintains context, so after starting, the container exits. We are going to have to be a bit hacky about this.. Trying to figure out what makes the most sense. I believe a startup script that waits is probably how we will address this.
docker run -m 2048m --ulimit nofile=64000:64000 -itp 8080:8080 -p 8443:8443 -v /home/ec2-user/opsmgr-conf.d/conf-mms.properties:/opt/mongodb-mms-126.96.36.1998-1.x86_64/conf/conf-mms.properties -v /home/ec2-user/opsmgr-conf.d/gen.key:/root/.mongodb-mms/gen.key --entrypoint /bin/bash myalenti/ops_manager