- 3,715,723 Users
- 2,242,844 Discussions
- 7,845,508 Comments
- 17 Data
- 362.2K Big Data Appliance
- 7 Data Science
- 1.6K Databases
- 467 General Database Discussions
- 22 Multilingual Engine
- 487 MySQL Community Space
- 3 NoSQL Database
- 7.6K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 416 SQLcl
- 42 SQL Developer Data Modeler
- 184.9K SQL & PL/SQL
- 21K SQL Developer
- 1.9K Development
- 3 Developer Projects
- 32 Programming Languages
- 135.1K Development Tools
- 9 DevOps
- 3K QA/Testing
- 248 Java
- 5 Java Learning Subscription
- 10 Database Connectivity
- 66 Java Community Process
- 1 Java 25
- 9 Java APIs
- 141.1K Java Development Tools
- 6 Java EE (Java Enterprise Edition)
- 153K Java Essentials
- 135 Java 8 Questions
- 86.2K Java Programming
- 270 Java Lambda MOOC
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 10 Java SE
- 13.8K Java Security
- 3 Java User Groups
- 18 Programs
- 125 LiveLabs
- 30 Workshops
- 9 Software
- 3 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 3 Deutsche Oracle Community
- 10 Español
- 1.9K Japanese
- 2 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.