Page History

...

• The JS7 Controller comes preinstalled from a Docker® container image.
• Initial operation for JS7 Controllers includes:
  
  • registering the Controller instance(s) and Agents that are used in the job scheduling environment.
  • optionally registering a JS7 Controller Cluster. 

...

This video explains how to install the JS7 Controller for Docker® containers:

...

Pull the version of the Controller container image that corresponds to the JS7 release in use, for example:

...

#!/bin/sh

docker run -dit --rm \
      --hostname=js7-controller-primary \
      --network=js7 \
      --publish=15444:4444 \
      --env="RUN_JS_JAVA_OPTIONS=-Xmx256m" \
      --env="RUN_JS_ID=jobscheduler" \
      --env="RUN_JS_USER_ID=$(id -u $USER):$(id -g $USER)" \
      --mount="type=volume,src=js7-controller-primary-var,dst=/var/sos-berlin.com/js7/controller/var" \
      --name js7-controller-primary \
      sosberlin/js7:controller-2-5-0

Explanation:

• --network The The above example makes use of a Docker container network - created with the docker network create js7 command  command - to allow network sharing between containers. Note that any inside ports used by Docker containers are is visible within a Docker container network. Therefore a Controller instance running for the inside port 4444 can be accessed using the container's hostname and the same port within the Docker container network.
• --publish The Controller is prepared to listen to the HTTP port 4444. An outside port of the Docker container's host can be mapped to the Controller's inside HTTP port. This is not required for use with a Docker container network, see --network, however, it will allow direct access to the Controller from the Docker Controller from the container's host through its outside port .
• --env=RUN_JS_JAVA_OPTIONS This allows to Java options to be injected into the Controller's container. Preferably this is used to specify memory requirements of a Controller, e.g. with -Xmx256m.
• --env=RUN_JS_ID This setting specifies the Controller ID that is a unique identifier for either a standalone Controller instance or for both the primary and secondary Controller instances in a cluster that use a common Controller ID.
• --env=RUN_JS_USER_ID Inside the container the Controller is operated with the jobscheduler user account. In order to access, for example, log files created by the Controller and mounted to the Docker container's host, it is recommended that you map the account that starts the container to the jobscheduler account inside the container. The RUN_JS_USER_ID environment variable accepts the User ID and Group ID of the account that will be mapped. The example listed above uses the current user, for details see JS7 - Running Containers for User Accounts.
• --mount The following volume mounts are suggested:
  • var: This folder works as an entry point to the following sub-folders:
    • config: The configuration folder allows the specification of  individual settings for the operation of the Controller - see the sections below and the JS7 - Controller Configuration Items article. Default settings are available from initial operation..
    • logs: In order to have persistent Controller log files they have to be written to a volume that is mounted for the container. Feel free to adjust the volume name from the src attribute, however, the value of the dst attribute should not be changed as it reflects the directory hierarchy inside the container.
    • state: The Controller requires a directory for journal information that should be persistent. The journal is required to restore the state of orders when restarting the Controller.

  • Docker Containers offers a number of ways of mounting volumes to containers, which include, for example, creating a local folder and mapping the folder to a volume before executing the docker run command listed above:

    Code Block
    language bash title Example how to create Docker volumes linenumbers true
    # example to map volumes to directories on the Docker host prior to running the Controller container mkdir -p /home/sos/js7/js7-controller-primary/var docker volume create --driver local --opt o=bind --opt type=none --opt device="/home/sos/js7/js7-controller-primary/var" js7-controller-primary-var

...

It is important that a time service is operated on the docker container's host which runs the Controller in order to synchronize the system clock's time.

...