- 385.1K All Categories
- 2.6K Data
- 623 Big Data Appliance
- 2K Data Science
- 452.3K Databases
- 222.5K General Database Discussions
- 32 Multilingual Engine
- 576 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 576 SQLcl
- 4K SQL Developer Data Modeler
- 187.8K SQL & PL/SQL
- 21.5K SQL Developer
- 14 Data Integration
- 14 GoldenGate
- 297.7K Development
- 3 Application Development
- 18 Developer Projects
- 140 Programming Languages
- 294.4K Development Tools
- 118 DevOps
- 3.1K QA/Testing
- 646.5K Java
- 30 Java Learning Subscription
- 37K Database Connectivity
- 186 Java Community Process
- 107 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 175 Java 8 Questions
- 86K Java Programming
- 82 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
- 206 Java User Groups
- 590 LiveLabs
- 41 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 5.8K Other Languages
- 2.3K Chinese
- 197 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 240 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.