Page History
...
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
#!/bin/sh docker run -dit --rm \ --user="$(id -u $USER):$(id -g $USER)" \ --hostname=js7-agent-primary \ --network=js7 \ --publish=16445:4445 \ --env="RUN_JS_JAVA_OPTIONS=-Xmx256m" \ --mount="type=volume,src=js7-agent-primary-config,dst=/var/sos-berlin.com/js7/agent/var_4445/config" \ --mount="type=volume,src=js7-agent-primary-logs,dst=/var/sos-berlin.com/js7/agent/var_4445/logs" \ --mount="type=volume,src=js7-agent-primary-state,dst=/var/sos-berlin.com/js7/agent/var_4445/state" \ --name js7-agent-primary \ sosberlin/jobschedulerjs7:agent-2-0-0-SNAPSHOT |
Explanations:
--user
Inside the container the Agent is operated for the user accountjobscheduler
. 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 thejobscheduler
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 commanddocker 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 port4445
is accessible with the container's hostname and the same port within the Docker network.--publish
The Agent is prepared to listen to the HTTP port4445
. An outside port of the Docker host can be mapped to the Agent's inside HTTP port. This is not required for use with a Docker network, see--network
, however, it will allow direct access to the Agent from the Docker host by its outside port .--env=RUN_JS_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
: The optional configuration folder allows to specify individual settings for Agent operation, see below chapters and the JS7 - Agent Configuration article. Without this folder the default settings are used.logs
: In order to have Agent 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 thesrc
attribute, however, the value of thedst
attribute should not be changed as it reflects the directory hierarchy inside the container.state
: The Agent requires a directory for journal information that should be persisted. The journal is required to restore the state of orders when restarting the Agent.
...
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
#!/bin/sh docker run -dit --rm \ ... --publish=16443:4443 \ --env="RUN_JS_HTTPS_PORT=16443" \ ... |
Explanations:
--publish
The Agent image is prepared to accept HTTPS requests on port4443
. If the Agent is not operated in a Docker network then an outside port of the Docker host has to be mapped to the inside HTTPS port4443
. The same port has to be assigned theRUN_JS_HTTPS_PORT
environment variable.--env=RUN_JS_HTTPS_PORT
The port assigned this environment variable is the same as the outside HTTP port specified with the--publish
option.
...
- When using HTTPS connections then consider to drop the HTTP port of the Agent by omitting the following above settings:
--publish=16445:4445
This mapping should be dropped in order to prevent incoming traffic to the Agent's HTTP port.--env=RUN_JS_HTTP_PORT
Without this setting the Agent will not listen to its HTTP port.
Overview
Content Tools