Mule Standalone Packaged by Bmeme

Mule Standalone docker images based on official Eclipse Temurin repository, currently used by Bmeme for Mule-based solutions.

What is contained in the images

• Mule, of course
• Eclipse Temurin openjdk

Supported tags and respective Dockerfile links

• 4.5.0-11, latest, Dockerfile
• 4.5.0-8, Dockerfile
• 4.4.0-11, Dockerfile
• 4.4.0-8, Dockerfile

Tag system

The tag of each image is composed by two values, separated by a -. The first one represents the Mule Standalone version. The second one represents the OpenJDK version.

How to use this image

Manually

Starting your Mule standalone environment is really simple:

$ docker run --name mymulecontainer \
    -v $DOMAINS_VOLUME_PATH:/opt/mule/domains \
    -v $APP_VOLUME_PATH:/opt/mule/apps \
    -v $RESOURCES_VOLUME_PATH:/opt/mule/resources \
    -p 8081:8081 -d bmeme/mule-standalone:latest

where:

• $DOMAINS_VOLUME_PATH represents the volume path of your Mule domain(s)
• $APP_VOLUME_PATH represents the volume path of your Mule apps
• $RESOURCES_VOLUME_PATH represents the volume path of your Mule app resource(s)

Using a Dockerfile

FROM bmeme/mule-standalone:latest

COPY /path/to/domains /opt/mule/domains
COPY /path/to/apps /opt/mule/apps
COPY /path/to/resources /opt/mule/resources

Then, run the commands to build and run the Docker image:

$ docker build -t mymuleimage:latest .
$ docker run -d --name mymulecontainer mymuleimage:latest

Using docker-compose

services:
  mule:
    image: bmeme/mule-standalone:latest
    ports:
      - 8081:8081
    volumes:
      - "/path/to/domains:/opt/mule/apps"
      - "/path/to/apps:/opt/mule/domains"
      - "/path/to/resources:/opt/mule/resources"

Credits

This project is a contribution of Bmeme :: The Digital Factory. This image is actually maintained by Daniele Piaggesi and Roberto Mariani. Any other contribution will be really appreciated.