This repository contains files necessary to build and run a Docker container for RAMADDA. The RAMADDA Docker images associated with this repository are available on Docker Hub.
unidata/ramadda-docker:latestunidata/ramadda-docker:2.2
To run the RAMADDA Docker container, beyond a basic Docker setup, we recommend installing docker-compose.
Customize the default docker-compose.yml to decide:
- which RAMADDA image you want to run
- which port will map to Tomcat port
8080 - which local directory will map to the RAMADDA
/data/repositorydirectory - which local directory will map to the Tomcat
/usr/local/tomcat/logsdirectory - which local directory will map to the RAMADDA
/data/repository/logsdirectory
Create the local directories defined in the docker-compose.yml for the RAMADDA /data/repository and /data/repository/logs directories, and the Tomcat /usr/local/tomcat/logs directory. For example:
mkdir repository tomcat-logs ramadda-logs
Inside the repository directory, create the pw.properties file. The contents of this .properties file will look something like:
ramadda.install.password=mysecretpassword
Replace mysecretpassword with the password of your choosing.
The Java (JAVA_OPTS) and Catalina (CATALINA_OPTS) are configured in:
${CATALINA_HOME}/bin/javaopts.sh(see javaopts.sh)${CATALINA_HOME}/bin/catalinaopts.sh(see catalinaopts.sh)
These files can be mounted over with docker-compose.yml which can be useful if, for instance, you wish to change the maximum Java heap space available to RAMADDA or other JVM and Catalina options.
Once you have completed your setup, run the container with:
docker-compose up -d
The output of such command should be something like:
Creating ramadda
To stop this container:
docker-compose stop
With Docker and docker-compose, updating software becomes easier. Update the container version in the docker-compose.yml (e.g., from unidata/ramadda-docker:2.2 to unidata/ramadda-docker:2.3), and stop and start the container with docker-compose.
To clean the slate and remove the container (not the image, the container):
docker-compose rm -f
At this point you should be able to do:
curl localhost:80/repository
# or whatever port you mapped to outside the container in the docker-compose.yml
and get back a response that looks something like
<!DOCTYPE html>
<html>
<head><title>Installation</title>
...
</html>
If you encounter a problem there, you can also:
docker ps
which should give you output that looks something like this:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7d7f65b66f8e unidata/ramadda-docker:latest "/bin/sh -c ${CATALIN" 21 hours ago Up 21 hours 8080/tcp, 0.0.0.0:80->8080/tcp ramaddadocker_ramadda_1
to obtain the ID of the running RAMADDA container. Now you can enter the container with:
docker exec -it <ID> bash
Now use curl inside the container to verify RAMADDA is running:
curl localhost:8080/repository
you should get a response that looks something like:
<!DOCTYPE html>
<html>
<head><title>Installation</title>
...
</html>
At this point we are done setting up RAMADDA with docker. To navigate to this instance of RAMADDA from the web, you will have to ensure your docker host (e.g., a cloud VM at Amazon or Microsoft Azure) allows Internet traffic through port 80 at whatever IP or domain name your docker host is located.