Page History

...

Line 1: The base image is OpenJDK Java 1.8 (Alpine based). You can run Controllers with newer Java releases, however, stick to Oracle, OpenJDK or AdoptOpenJDK as the source for your Java base image. Alternatively you can use your own base image and install Java 1.8 on top of this.
Line 8 - 9: The release identification is injected by build arguments. This information is used to determine the tarball to be downloaded.
Line 12 - 18: Defaults for the Controller ID and user id running the Controller inside the container as well as HTTP and HTTPS ports are provided. These values can be overwritten by providing the respective build arguments.
Line 23 - 28: Environment variables are provided at run-time, not at build-time. They can be used to specify ports and Java options when running the container.
Line 33 - 36: The image OS is updated and additional packages are installed (ps, netstat, bash, vi).
Line 43 - 44: You can either download the Controller tarball directly from the SOS web site or you store the tarball with the build directory and copy from this location.

Line 47: The start-controller.sh script is copied from the build directory to the image. Users can apply their own version of the start script. The start script used by SOS looks like this:

Code Block

language	bash
title	Controller Start Script
linenumbers	true
collapse	true

#!/bin/sh

js_id=""
js_http_port=""
js_https_port=""
js_java_options=""

for option in "$@"
do
  case "$option" in
         --id=*)           js_id=`echo "$option" | sed 's/--id=//'`
                           ;;
         --http-port=*)    js_http_port=`echo "$option" | sed 's/--http-port=//'`
                           ;;
         --https-port=*)   js_https_port=`echo "$option" | sed 's/--https-port=//'`
                           ;;
         --java-options=*) js_java_options=`echo "$option" | sed 's/--java-options=//'`
                           ;;
         *)                echo "unknown argument: $option"
                           exit 1
                           ;;
  esac
done

js_args=""

if [ ! "$js_http_port" = "" ] && [ ! "$js_http_port" = ":" ]
then
  js_args="$js_args --http-port=$js_http_port"
fi

if [ ! "$js_https_port" = "" ] && [ ! "$js_https_port" = ":" ]
then
  js_args="$js_args --https-port=$js_https_port"
fi

if [ ! "$js_java_options" = "" ]
then
  js_args="$js_args --java-options=$js_java_options"
fi

echo "starting Controller: /var/sos-berlin.com/js7/controller/bin/controller.sh start --id=$js_id $js_args"
/var/sos-berlin.com/js7/controller/bin/controller.sh start --id=$js_id $js_args && tail -f /dev/null

Line 54 - 6259: The user account jobscheduler is created and is assigned the user id and group id handed over by the respective build arguments. This translates to the fact that the account running the Controller inside the container and the account that starts the container are assigned the same user id and group id. This allows the account running the container to access any files created by the Controller in mounted volumes with identical permissions.
Line 5860: Java releases < Java 12 make use of /dev/random for random number generation. This is a bottleneck as random number generation with this file is blocking. Instead /dev/urandom should be used that implements non-blocking behavior. The change of the random file is applied to the Java security file.
Line 65: if a config folder is available in the build directory then its contents is copied to the respective config folder in the image. This can be useful to create an image with individual settings in configuration files, see JS7 - Controller Configuration Items.
Line 72: The start script is executed and is dynamically parameterized from environment variables that are forwarded when starting the container.

...

Space shortcuts

Page tree

Versions Compared

Old Version 12

New Version 13

Key