Author Topic: Docker image for JTS3ServerMod  (Read 140 times)

PhALDan

  • Newbie
  • *
  • Posts: 3
    • View Profile
Docker image for JTS3ServerMod
« on: September 06, 2017, 05:03:51 PM »


I've created a Docker image for the JTS3ServerMod some time ago and until today this image has almost 3k downloads. This image is the most downloaded image for the JTS3ServerMod and I thought it would be interesting for some folks here. The first part is about using the Docker image and the second part is an introduction into docker, because not everyone knows what Docker is. This image is size optimised and is based on the official openjdk:8-jre-alpine image. More information about the image can be found on the page at the official Docker Hub.

Running the Docker image:
Code: [Select]
$ docker run --name jts3servermod -d -v ${PWD}/config:/JTS3ServerMod/config -v ${PWD}/log:/JTS3ServerMod/log phaldan/jts3servermod
As seen in the command for running the image the installation is located in the /JTS3ServerMod folder inside the image and from there different parts of the JTS3ServerMod can be mount with volumes into the image like the configuration or the log folder. Differently then in the official JTS3ServerMod the log files like the JTS3ServerMod_InstanceManager.log are located in the log folder at the image. Within a Docker images it makes more sense to have a specific folder for the log files and with this solution it is much easier to write these log files to the host or another file system.

What is Docker?
Docker is the world’s leading software container platform. Developers use Docker to eliminate “works on my machine” problems when collaborating on code with co-workers. Operators use Docker to run and manage apps side-by-side in isolated containers to get better compute density. Enterprises use Docker to build agile software delivery pipelines to ship new features faster, more securely and with confidence for both Linux, Windows Server, and Linux-on-mainframe apps.

Containers are a way to package software in a format that can run isolated on a shared operating system. Unlike VMs, containers do not bundle a full operating system - only libraries and settings required to make the software work are needed. This makes for efficient, lightweight, self-contained systems and guarantees that software will always run the same, regardless of where it’s deployed.

More information can be found at the official Docker website.

Please let me know if you have any questions or need more information.