Introduction

The JS7 - Controller Installation for Docker Containers article explains start-up of a Controller container using the Docker® Run run command.

The following examples apply for users who wish to start containers using the docker-compose utility. Note that examples have to be adjusted to suit individual environments.

Examples are have been contributed by the Japanese JS7 Community. Find the The complete instructions from can be found in the Start with JS7 JobScheduler docker-compose (MySQL version) article.

...

• Use of volumes: There are a number of ways of mounting or binding volumes into a container.
  • One strategy is to mount a Docker® volume which is managed by Docker®, typically in /var/lib/docker/volumes.
  • Another strategy is to map Docker® volumes to the local file system. This requires letting Docker® Compose know that the volume is locally managed and is the in focus of the above example.
• Use of user accounts: see JS7 - Running Containers for User Accounts.
  • The RUN_JS_USER_ID setting holds the User ID and Group ID. Consider that the Group ID has to be 0  as directories and files in the image are owned by the root group.

Environment Variables used with the Examples

echo -e "JS7USERID=$(id -u)\nJS7GROUPID=$(id -g)\nJS7VERSION=2-35-20" > .env

# check environment variables
cat .env
JS7USERID=1000
JS7GROUPID=10000
JS7VERSION=2-35-20

Directories used with the Examples

...

docker-compose up -d

# check containers
$ docker-compose ps
NAME                            COMMAND                  SERVICE                  STATUS              PORTS
js74-js7-controller-primary-1   "sh /usr/local/bin/e…"   js7-controller-primary   running             

Initial Operation

See JS7 - Controller Installation for Docker Containers, section: Initial Operation.