Sunday, March 5, 2017

Adding Examples to a Docker Container with Oracle database 12.2

Oracle Database 12.2 became available for download last week. This weekend I've been playing with Docker and created a container with it. The whole process is so easy, thanks to the work by Gerald Venzl at Oracle. You'll find all the information you need in his blog post. Though the post is for version, the dockerfiles have already been updated for, and you can download it from Github using the link he provides in the post.

It takes sometime to create a container (depending on your hardware, of course), so when I discovered that the examples / demos that are distributed in another file were not included, I decided to try to add it to the running container.  It is easy, just download the file and copy it into the running container, which in my case is named ora12.2:

docker cp ora12.2:/tmp

Also unzip a copy of the included response file locally:
unzip -j -d /tmp \

Edit it and change the variables so they look like this:


Copy it to the container:
docker cp /tmp/demos_install.rsp ora12.2:/tmp

Connect to your container with a command similar to this (again, ora12.2 is the name of my container):

docker exec -ti ora12.2 /bin/bash

Inside the container, unzip the transferred zip file and start the installation with:

cd /tmp
cd examples
./runInstaller -silent -force -waitforcompletion \
-responsefile /tmp/demos_install.rsp  -ignoresysprereqs -ignoreprereq

You can now verify that you have more demos installed, for instance under $ORACLE_HOME/md/demo.

Of course you can achieve the same effect by adding a few lines to the Dockerfile, build, and run again. Something like this should do for the Dockerfile:

# Added install of examples 
ENV EXAMPLE_RSP="demos_install.rsp" \
RUN cd /tmp && \
  unzip && \
  cd examples && \
  ./runInstaller -silent -force -waitforcompletion \
  -responsefile /tmp/demos_install.rsp  -ignoresysprereqs -ignoreprereq

It turned out to run just as fast since the new build builds on the previous images, oh well.


Frank M. said...

Hi Øyvind,

Good to see more DB and Docker blog postings!
If you you do the docker cp & exec trick, be careful since it won't persist your changes.
You will only have them in the running container, but not in the image.
So make sure to run docker commit at the end.

Somehow like with a DB :-).

As you mention, recreate the image is usually best.

all the best &
hope to see you at OUGN!


Oyvind Isene said...

Thank you, important tip; I was more in a lab mood without fear of losing anything when doing this :-) Looking forward to see you at the ship!