ops-manager-init container issue
Summary
container doesn't run. Issue in entrypoint no /opt/scripts directory
Steps to reproduce
docker run registry1.dso.mil/ironbank/mongodb/mongodb-enterprise/mongodb-ops-manager-init
What is the current bug behavior?
running the container errors with:
cp: target '/opt/scripts/' is not a directory
What is the expected correct behavior?
container startup
Relevant logs and/or screenshots
# docker run registry1.dso.mil/ironbank/mongodb/mongodb-enterprise/mongodb-ops-manager-init
cp: target '/opt/scripts/' is not a directory
Possible fixes
Defintion of Done
-
Bug has been identified and corrected within the container and new image is in ironbank
/cc @ironbank-notifications/bug
Edited by Branden Cobb