Page History

...

Line 8 - 9: The release identification is injected by build arguments. This information is used to determine the tarball to be downloaded with line 35
Line 12 - 15: Defaults for the user id running the Agent inside the container as well as HTTP and HTTPS ports are provided. These values can be overwritten by providing the respective build arguments.
Line 20 - 22: 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 5049: if a config folder is available in the build folder then its contents is copied to the respective config folder in the container. This can be used to create an image with updated configuration files, see JS7 - Agent Configuration Items.

Line 5352: The start-agent.sh script is copied from the build folder to the container. Users can apply their own version of the start script. The start script used by SOS looks like this:

Code Block

language	bash
title	Agent Start Script
linenumbers	true
collapse	true

#!/bin/sh

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

for option in "$@"
do
  case "$option" in
         --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" = "" ]
then
  js_args="$js_args --http-port=$js_http_port"
fi

if [ ! "$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 Agent: /var/sos-berlin.com/js7/agent/bin/agent.sh start $js_args"
/var/sos-berlin.com/js7/agent/bin/agent.sh start $js_args && tail -f /dev/null

Line 56 55 - 5857: The user account jobscheduler is created and is assigned the user id and group id handed over by the respective build argument. This translates to the fact that the account running the Agent 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 Agent in mounted volumes with identical permissions.
Line 6665: The HTTP and optionally the HTTPS port that are forwarded by environment variables when running the container are exposed to the Docker host. This is relevant only if users wanted to use ports inside the container that are different from the default values. In most situations the default ports should be fine and are mapped to outside ports on the Docker host when starting the container.
Line 6867: 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 5

New Version 6

Key