thomas67/mule-ee-docker repository overview

⁠Standalone Mule ESB Enterprise Docker Image

This project contains a Dockerfile for the deployment and packaging of a standalone Mule ESB Enterprise with Docker.

⁠Preparing the Docker base image

Due to restrictions of the Enterprise version, the Docker image needs to be set up for individual usage beforehand. It is required to:

• provide the Enterprise standalone server from Mulesoft. In this Dockerfile we asume the downloaded trial version from mulesoft.com⁠, located in the same folder as the Dockerfile.
• provide the Enterprise license file from Mulesoft, located in the same folder as the Dockerfile.

Hence the directory should look like this:

• mule-ee/
• mule-ee/Dockerfile
• mule-ee/start.sh

⁠Building and tagging the Docker base image

docker build --tag="thomas67/mule-ee" .

⁠Using the Docker image

You can create an Docker image for each Mule ESB application to isolate applications from each other and this way startup and create multiple standalone Mule ESB instances.

⁠Standalone Mule ESB Enterprise Container

Start a standalone Mule ESB Enterprise instance

docker run -t -i --name='mule-ee-instance-X' thomas67/mule-ee

⁠App specific container image

FROM                    thomas67/mule-ee:latest
.
.
ADD                     mule-app/target/mule-app-1.0.0-SNAPSHOT.zip /opt/mule/apps/

Build application specific Docker image:

docker build --tag="my-mule-app-image" .

Start app specific image:

docker run -t -i --name='mule-app-node' my-mule-app-image
for example (including externally mountable apps directory):
docker run -it --name='mule-ee' -v `pwd`/apps:/opt/mule/apps thomas-li/mule-ee