- 381.9K All Categories
- 2.1K Data
- 207 Big Data Appliance
- 1.9K Data Science
- 447.4K Databases
- 220.8K General Database Discussions
- 23 Multilingual Engine
- 516 MySQL Community Space
- 463 NoSQL Database
- 7.8K Oracle Database Express Edition (XE)
- 2.9K ORDS, SODA & JSON in the Database
- 469 SQLcl
- 3.9K SQL Developer Data Modeler
- 185.9K SQL & PL/SQL
- 20.9K SQL Developer
- 292.6K Development
- 7 Developer Projects
- 124 Programming Languages
- 289.4K Development Tools
- 95 DevOps
- 3K QA/Testing
- 645.5K Java
- 23 Java Learning Subscription
- 36.9K Database Connectivity
- 150 Java Community Process
- 104 Java 25
- 22.1K Java APIs
- 137.8K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 16 Java Essentials
- 143 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 197 Java User Groups
- 243 LiveLabs
- 35 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.8K Other Languages
- 2.3K Chinese
- 166 Deutsche Oracle Community
- 1.2K Español
- 1.9K Japanese
- 225 Portuguese
Using the docker image
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.
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.