## Summary ops-manager container wont run due to issues in the entrypoint command. ## Steps to reproduce docker run registry1.dso.mil/ironbank/mongodb/mongodb-enterprise/mongodb-enterprise-ops-manager ## What is the current bug behavior? container errors with: ``` docker: Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: exec: "/mongodb-ops-manager/bin/mongodb-mms start_mms": stat /mongodb-ops-manager/bin/mongodb-mms start_mms: no such file or directory: unknown. ERRO[0000] error waiting for container: context canceled ``` ## What is the expected correct behavior? container startup ## Relevant logs and/or screenshots ``` # docker run registry1.dso.mil/ironbank/mongodb/mongodb-enterprise/mongodb-enterprise-ops-manager docker: Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: exec: "/mongodb-ops-manager/bin/mongodb-mms start_mms": stat /mongodb-ops-manager/bin/mongodb-mms start_mms: no such file or directory: unknown. ERRO[0000] error waiting for container: context canceled ``` ## Possible fixes https://repo1.dso.mil/dsop/mongodb/mongodb-enterprise/mongodb-enterprise-ops-manager/-/blob/master/Dockerfile#L44 ## Defintion of Done - [ ] Bug has been identified and corrected within the container and new container uploaded to ironbank /cc @ironbank-notifications/bug