Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 238 Big Data Appliance
- 1.9K Data Science
- 450.3K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 544 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.8K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.5K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 437 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Using the docker image

commi235
Member Posts: 28 Blue Ribbon
Hi all,
I was stumbling over the same thing that Lucas had in another thread.
So I thought to write a quick guide to running the mle-docker image.
First thing:
I'm in no way an expert when it comes to docker.
There might be an easier way, but I don't know any better yet.
This is how far I got until now:
- Download the mle-docker-0.2.7.tar.gz to your machine.
- Switch to the directory where you downloaded the file.
- Load the image:
docker load -i mle-docker-0.2.7.tar.gz
( I know there is also docker import command, but I ran into issues when using that one. ) - Wait until docker has finished it's job. (Get a coffee )
- docker images
Check out which Image ID you got. - Run the image:
docker run -itP --name <your_choice> <image_id>
This will keep the output open and map all ports which should be exposed to some random port on your host machine. - Wait until everything is set up, it will show you a tail of the alert log when finished. (More coffee )
This really takes a while, but to be fair it sets up a complete database when first started. - Get yourself a shell:
docker exec -it mle-docker /bin/bash
I haven't yet tried out to load some JS into the DB but that's for another time.
Hth,
Moritz