Pulling the JOC Cockpit Image

Pull the version of the JOC Cockpit image that corresponds to the JS7 release in use:

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

Running the JOC Cockpit Container

After pulling the JOC Cockpit image you can run the container with a number of options like this:

#!/bin/sh

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

Explanations:

• --user Inside the container the JOC Cockpit instance is operated for the user account jobscheduler. In order to access e.g. log files created by the JOC Cockpit instance 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 the command 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 a JOC Cockpit instance running for the inside port 4446 is accessible with the container's hostname and the same port within the Docker network.
• --publish The JOC Cockpit is prepared to listen to the HTTP port 4446. An outside port of the Docker host can be mapped to the JOC Cockpit inside HTTP port. This is not required for use with a Docker network, see --network, however, it will allow direct access to the JOC Cockpit from the Docker host by its outside port .
• --env=RUN_JS_HTTP_PORT Consider to specify the same outside port that is used with the --publish option to map an outside port to the inside HTTP port.
• --env=JAVA_OPTIONS This allows to inject any Java options to the JOC Cockpit container. Preferably this is used to specify memory requirements of JOC Cockpit, e.g. with -Xmx256m.
• --mount The following volume mounts are suggested:
  • config: The optional configuration folder allows to specify individual settings for JOC Cockpit operation, see below chapters and the JS7 - JOC Cockpit Configuration article. Without this folder the default settings are used.
  • logs: In order to have JOC Cockpit log files persisted 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.

Configuring the JOC Cockpit