https://github.com/levigo/jadice-server-docker
Dockerfile for building a docker image containing the levigo jadice server
https://github.com/levigo/jadice-server-docker
docker jadice-server levigo
Last synced: over 1 year ago
JSON representation
Dockerfile for building a docker image containing the levigo jadice server
- Host: GitHub
- URL: https://github.com/levigo/jadice-server-docker
- Owner: levigo
- License: bsd-3-clause
- Created: 2017-02-13T15:39:25.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2022-10-11T14:03:21.000Z (over 3 years ago)
- Last Synced: 2025-03-04T13:46:13.191Z (over 1 year ago)
- Topics: docker, jadice-server, levigo
- Language: Dockerfile
- Size: 40 KB
- Stars: 1
- Watchers: 17
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
README
# levigo _jadice server_ Docker Container
# Table of Contents
1. [Introduction](#introduction)
1. [Requirements](#requirements)
1. [Environment variables](#environment-variables)
1. [Configuration](#configuration)
1. [Logging](#logging)
1. [docker-compose](#docker-compose)
## Introduction
This repository contains a `Dockerfile` for building a docker image containing the levigo [_jadice server_](https://jadice.com/produkte/server/).
It is provided "as is", see [LICENSE.md](https://github.com/levigo/jadice-server-docker/blob/master/LICENSE.md).
The image is based on [openjdk:11.0.8-jre-buster](https://hub.docker.com/_/openjdk).
## Requirements
* You need version 5.8.0.0 or newer of the _jadice server_ distribution to use _jadice server_ in a docker container with Java 11.
For more information on how to get the _jadice server_ distribution visit [jadice.com](https://www.jadice.com).
* docker-engine 17.06 or newer is required for building and running the Image.
* docker-compose version 1.16.0 or newer for the use of docker-compose.yml.
* For running jadice-server with Java 8 you can checkout the branch _java8_. This requires version 5.5 or newer of the _jadice server_ distribution.
## Building the Image
* Copy the _jadice server_ distribution zip into the resources directory.
* Apply customization if needed (see [Configuration](#configuration))
* Run:
```sh
docker build -t= .
docker run -p 61616:61616
```
## Environment variables
_jadice server_ evaluates the following environment variables during start.
- `spring.profiles.active` - active features for jadice server (see also `/server-config/application/active-features.xml`)
- `jadice.server.activemq-host` - set the Apache ActiveMQ broker host (by default _jadice server_ starts its own broker on localhost)
## Configuration
In order to customize the configuration of _jadice server_ you need to copy your existing configuration into the subfolder `customization`. The docker build will copy all files into the directory `/` inside the container.
## Logging
There are two ways to access the logs from _jadice server_:
- mount an extra volume for log files
- use the docker logging driver
_jadice server_ writes logs by default to `/logs`. To access the log files, mount some directory from the host and _jadice server_ will write the files in the host's file system.
```sh
docker run -v :/opt/jadice-server/logs
```
Also the logs are available over the docker logs functionality.
## docker-compose
The `docker-compose.yml` shows an example implementation of the [Compose](https://docs.docker.com/compose/compose-file/compose-file-v2/) file for _jadice server_.
The docker-compose file defines three services:
- js-amq - a _jadice server_ instance with only the embedded-broker activated
- js-convert - a convert instance of _jadice server_
- js-webservice - the webservice entrypoint
docker-compose.yml uses the [environment variables](#environment-variables) to configure the active features for _jadice server_ instances.
All three services connect together over the js-amq instance. To submit jobs to the _jadice server_ you can either use the webservice interface or the default JMS interface. Both submit jobs to the JMS request queue which is consumed by the js-convert instance.