Public | Automated Build

Last pushed: 8 months ago
Short Description
Base image of Drools 7. This image comes from the jboss official image.
Full Description

Drools Workbench Docker image

JBoss Drools Workbench Docker image.

Table of contents

  • Introduction
  • Usage
  • Users and roles
  • Logging
  • GIT internal repository
  • Extending this image
  • Experimenting
  • Notes
  • Release notes


The image contains:

  • JBoss Wildfly 10.0.0.Final
  • JBoss Drools Workbench 6.5.0.Final

This image provides the JBoss Drools Workbench web application. It's intended to be extended so you can add your custom configurations.

If you don't want to extend this image and you just want to try Drools Workbench, please take a look at the jboss/drools-workbench-showcase:latest Docker image, it contains some default configurations.


To run a container:

docker run -p 8080:8080 -p 8001:8001 -d --name drools-workbench jboss/drools-workbench:latest

Once container starts, you can navigate into the Drools Workbench at:


Users and roles

The application have no users or roles configured, so you cannot not access it by default,

In order to use it, at least you have to create an application user in JBoss Wildfly with role admin.

If you are looking for a Drools Workbench image that does not require to add custom configurations, try our jboss/drools-workbench-showcase:latest Docker image.

If you want to create your custom configuration and users, role, etc, you can take a look at section Extending this image


You can see all logs generated by the standalone binary running:

docker logs [-f] <container_id>

You can attach the container by running:

docker attach <container_id>

The Drools Workbench web application logs can be found inside the container at path:


sudo nsenter -t $(docker inspect --format '{{ .State.Pid }}' $(docker ps -lq)) -m -u -i -n -p -w
-bash-4.2# tail -f /opt/jboss/wildfly/standalone/log/server.log

GIT internal repository

The workbench stores all the project artifacts in an internal GIT repository. By default, the protocol available for accessing the GIT repository is SSH at port 8001.

You can clone the GIT repository by running:

git clone ssh://admin@localhost:8001/system

By default, the GIT repository is created when the application starts for first time at $WORKING_DIR/.niogit, considering $WORKING_DIR as the current directory where the application server is started.

You can specify a custom repository location by setting the following Java system property to your target file system directory:


NOTE: This directory can be shared with your docker host and with another containers using shared volumes when running the container, if you need so.

If necessary you can make GIT repositories available from outside localhost using the following Java system property:

You can set this Java system properties permanent by adding the following lines in your standalone-full.xml file as:

      <!-- Custom repository location. -->
      <property name="org.uberfire.nio.git.dir" value="/home/youruser/some/path"/>
      <!-- Make GIT repositories available from outside localhost. -->
      <property name="" value=""/>

NOTE: Users and password for ssh access are the same that for the web application users defined at the realm files.

Extending this image

You can extend this image and add your custom layers in order to add custom configurations, users, roles, etc.

In order to extend this image, your Dockerfile must inherit from:

FROM jboss/drools-workbench:latest

Configuring Wildfly

  • The Wildfly configuration files are located at /opt/jboss/wildfly/standalone/configuration
  • In this file you can modify all Wildfly's subsystem configurations
  • Drools Workbench requires running Wildfly using full profile, so custom modifications should be done in standalone-full.xml configuration file

Users and roles

  • By default this image does not provide users and roles for Drools Workbench

  • The available roles for Drools Workbench examples are:

      admin       The administrator
      analyst     The analyst
      developer   The developer
      manager     The manager
      user        The end user
      kiemgmt     KIE management user
      Accounting  Accounting role
      PM          Project manager role
      HR          Human resources role
      sales       Sales role
      IT          IT role

These are the steps to create your custom users and roles by using realm files in Widlfly:

1.- Create a realm properties file for users and deploy it in /opt/jboss/wildfly/standalone/configuration:

2.- Create a realm properties file for roles and deploy it in /opt/jboss/wildfly/standalone/configuration:

3.- Modify your standalone-full.xml in order to:

3.1 - In the management section, modify default the security-realm for the ApplicationRealm as:

    <security-realm name="ApplicationRealm">
            <local default-user="$local" allowed-users="*" skip-group-loading="true"/>
            <properties path="" relative-to="jboss.server.config.dir"/>
            <properties path="" relative-to="jboss.server.config.dir"/>

3.2 - In the security subsystem, modify default the other security-domain for as:

    <security-domain name="other" cache-type="default">
        <login-module code="UsersRoles" flag="required">
          <module-option name="usersProperties" value="${jboss.server.config.dir}/"/>
          <module-option name="rolesProperties" value="${jboss.server.config.dir}/"/>

You can find an example by looking at the Dockerfile for jboss/drools-workbench-showcase:latest image.


To spin up a shell in one of the containers try:

docker run -p 8080:8080 -p 8001:8001 -d --name drools-workbench jboss/drools-workbench:latest /bin/bash

You can then noodle around the container and run stuff & look at files etc.


  • The context path for Drools Workbench web application is drools-wb
  • Drools Workbench version is 6.5.0.Final
  • Drools Workbench requires running JBoss Wildfly using the full server profile
  • No users or roles are configured by default
  • Examples and demos disabled by default (no internet connection required at startup)
  • No support for clustering
  • Use of embedded H2 database server by default
  • No support for Wildfly domain mode, just standalone mode
  • This image is not intended to be run on cloud environments such as RedHat OpenShift or Amazon EC2, as it does not meet all the requirements.
  • Please give us your feedback or report a issue at Drools Setup or Drools Usage Google groups.

Release notes


  • Use Wildfly 10.0.0.Final
  • Upgrade app to version 6.5.0.Final
  • Disabled examples (no internet connection required at startup)
  • Added KIE_DEMO environment variable to disable examples and demos if host do not have internet connection
Docker Pull Command
Source Repository