- 3,727,564 Users
- 2,245,413 Discussions
- 7,852,880 Comments
- 380.8K All Categories
- 16 Data
- 362.2K Big Data Appliance
- 7 Data Science
- 2.3K Databases
- 684 General Database Discussions
- 32 Multilingual Engine
- 499 MySQL Community Space
- 10 NoSQL Database
- 7.7K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 424 SQLcl
- 69 SQL Developer Data Modeler
- 185.2K SQL & PL/SQL
- 21.1K SQL Developer
- 2.7K Development
- 3 Developer Projects
- 32 Programming Languages
- 135.9K Development Tools
- 18 DevOps
- 3K QA/Testing
- 385 Java
- 16 Java Learning Subscription
- 14 Database Connectivity
- 72 Java Community Process
- 3 Java 25
- 14 Java APIs
- 141.2K Java Development Tools
- 14 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
- 18 Java SE
- 13.8K Java Security
- 4 Java User Groups
- 18 Programs
- 157 LiveLabs
- 36 Workshops
- 11 Software
- 5 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 4 Deutsche Oracle Community
- 17 Español
- 1.9K Japanese
- 4 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.