WARNING: THIS DOCKER IMAGE IS NOT FOR PRODUCTION USAGE !!!
USE AT YOUR OWN RISK!
- This project is meant to help users try out particular Ops Manager versions (configurable in the Makefile); it is NOT suited for PRODUCTION use!!!
- When targeting arm64 (aarch64), the build process replaces the original x64 JDK11
- You may need to update the JDK link for newer OM versions
- Ops Manager needs a running MongoDB to serve as an AppDB; the
buildandrunphases will start amongo:5container, exposed to the host on port38017; this does not use authentication, a.k.a. it is INSECURE! - During build, Ops Manager is started, which pregenerates
/etc/mongodb-mms/gen.key, a.k.a. it is INSECURE! - This image DOES NOT start a Backup Daemon
- This is image is targeted at arm64 but also builds and runs on the
x86_64architecture. - DO NOT USE in PRODUCTION !!!
- Docker Desktop (tested on
4.8.2 (79419))
- 1. Checkout this repo and build the image
git clone git@github.com:mongodb-labs/omida.git
cd omida
make clean build- 2. Start the AppDB and Ops Manager
make run- 3. Wait for the Ops Manager service to start at http://localhost:9080
Enjoy!
- tests were performed locally, over WiFi
- these timings are mostly informative, are are not to be seen as guarantees!
make clean build: 1:36mmake run(cold start): 3:44mmake run: 1:46m
make clean build: 0:45mmake run(cold start): 2:50mmake run: 1:20m
- edit the Makefile
- set
VERSION=[your desired version] - Rebuild the image
docker clean build
NOTE: if building on
arm64, you might also need to updateJDK_ARM64_BINARY(see below)
- find the latest Linux arm JDK release on Adoptium.net (to do this, look for a string similar to
If the download doesn't start in a few seconds, please _click here_ to start the download., right click onclick hereand copy the link) - edit the Makefile
- update the
JDK_ARM64_BINARY=variable - run
make clean build
Occasionally, you may run out of space, especially if you repeatedly run make clean build.
In that case, run make clean && docker volume prune to clean up space.
Additionally, try deleting the MongoDB docker image (docker rmi mongo:5), which will fail but identify
previously started containers, associated with this image.