images

LOCI: images

This directory contains a Dockerfile for building a Loci Java layer docker container. Rather than deploying the software as a series of jar's in a tarball, we create a docker container and export that to the control computer.

Deployment

Java layer docker

To build a docker container do the following (on an LT development machine, where the loci software repository is installed at /home/dev/src/loci) :

• cd ~dev/src/loci/images (i.e. this directory)
• ./provision_loci Run the provisioning script, which copies the Java libraries from /home/dev/bin/javalib, and the C libraries from /home/dev/bin/lib/x86_64-linux/, into a created docker directory tree (created in the images directory). This allows us to use a local context for the docker build.
• docker build -f loci_java_layer -t loci_java_layer_image . Build the docker container from the loci_java_layer file.
• docker save -o loci_java_layer_image.tar loci_java_layer_image Save the constructed docker container into the loci_java_layer_image.tar tarball.

This saved docker tarball can then be copied to loci1 (the Loci control computer) as follows:

• gzip loci_java_layer_image.tar
• scp -C loci_java_layer_image.tar.gz user@loci1:/loci-containers

The docker can then be installed / loaded into the local system as follows:

• ssh user@loci1
• cd /loci-containers
• gunzip loci_java_layer_image.tar.gz
• docker load -i loci_java_layer_image.tar

You now need to install the Loci Java layer config files before starting the docker.

Java layer config files

To generate a tarball containing the Loci Java layer config files, on an LT development machine , where the loci software repository is installed at /home/dev/src/loci, do the following:

• cd ~dev/src/loci/scripts/
• ./loci_create_config_tarball This currently uses the docker. version of the config files.

The config tarball ends up at: ~dev/public_html/loci/deployment/loci_config_deployment.tar.gz . Copy the config tarball to loci1:

• scp -C ~dev/public_html/loci/deployment/loci_config_deployment.tar.gz user@loci1:Downloads

Then install the config tarball as follows:

• ssh user@loci1
• cd /
• sudo tar xvfz /home/user/Downloads/loci_config_deployment.tar.gz
• sudo chown root:root / This fixes root's permissions.

Starting the Loci Java layer

The Loci Java layer can then be started as follows:

• docker run -p 7679:7679 -p 8473:8473 --mount type=bind,src=/icc,dst=/icc --mount type=bind,src=/data,dst=/data --name=loci-java-layer -it -d --restart unless-stopped loci_java_layer_image

For this to work the Loci Java layer config files need to have been installed under /icc first.

An explanation of the command line:

• -p 7679:7679 -p 8473:8473 : allow access via ports 7679, 8473
• --mount type=bind,src=/icc,dst=/icc : allow docker to access /icc as /icc to load java layer config files, and write logs
• --mount type=bind,src=/data,dst=/data : allow docker to access /data as /data to access FITS images written by the Loci CCD Flask API. These actually only need accessing for the TITServer, which can transfer them back to the ics_gui.
• --name=loci-java-layer docker is called loci-java-layer in docker ps
• -d : docker is a daemon (detach from terminal)
• --restart unless-stopped : restart docker on exit, unless it has been explicitly stopped using docker kill
• -it : -t allocate a pseodo-tty, -i interactive. Do we need these?

Stopping the Loci Java layer

The Loci Java layer can be stopped as follows:

• sudo docker ps Find the loci-java-layer container id and then do the following:

• sudo docker kill <containerid>

• sudo docker remove <containerid>

You need to remove the container to re-use the loci-java-layer container name.