Download Image

Download the version of  the Agent image that corresponds to the JS7 release in use:

docker image pull sosberlin/jobscheduler:agent-2-0-0

Run Container

After pulling the Agent image you can 

#!/bin/sh

docker run -dit --rm \
      --user="$(id -u $USER):$(id -g $USER)" \
      --hostname=js7-agent-2-0-primary \
      --network=js7 \
      --publish=14445:4445 \
      --env="RUN_JS_HTTP_PORT=14445" \
      --env="RUN_JS_JAVA_OPTIONS=-Xmx256m" \
      --mount="type=volume,src=js7-agent-2-0-primary-config,dst=/var/sos-berlin.com/js7/agent/var_4445/config" \
      --mount="type=volume,src=js7-agent-2-0-primary-logs,dst=/var/sos-berlin.com/js7/agent/var_4445/logs" \
      --mount="type=volume,src=js7-agent-2-0-primary-state,dst=/var/sos-berlin.com/js7/agent/var_4445/state" \
      --name js7-agent-2-0-0-primary \
      sosberlin/jobscheduler:agent-2-0-0

Explanations:

• --user Inside the container the Agent is operated for the user account jobscheduler. In order to access e.g. log files created by the Agent that are mounted to the Docker host it is recommended that you map the account that is starting the container to the jobscheduler account inside the container. The --user option accepts the user ID and group ID of the account that will be mapped. The above example makes use of the current user.
• --network The above example makes use of a Docker network - created e.g. with docker network create js7 - to allow network sharing between containers. Consider that any inside ports used by Docker containers are visible within a Docker network. Therefore an Agent running for the inside port 4445 is accessible from the container's hostname and the same port.
• --publish An outside port of the Docker host is mapped to the Agent's inside HTTP port. This is not required for use with a Docker network, see --network, however, it will allow to directly access the Agent by its outside port from the Docker host.
• --env=RUN_JS_HTTP_PORT Consider to specify the same outside port that is used when mapping an outside port to the inside HTTP port with the --publish option.
• --env=JAVA_OPTIONS This allows to inject any Java options to the Agent's container. Preferably this is used to specify memory requirements of an Agent, e.g. with -Xmx256m.
• --mount The following volume mounts are suggested:
  • config:
  • logs: In order to have Agent log files persisted they should be written to a volume that is mounted for the Agent. Feel free to adjust the volume name from the src attribute, however, the value of the dst attribute should no be changed as it reflects the directory hierarchy inside the container.
  • state: The Agent requires a directory for journal information that should be persisted.