updated mule ee to 3.8.5 and converting to an automated build
100K+
This project contains a Dockerfile for the deployment and packaging of a standalone Mule ESB Enterprise with Docker.
Due to restrictions of the Enterprise version, the Docker image needs to be set up for individual usage beforehand. It is required to:
Hence the directory should look like this:
docker build --tag="mule-ee" .
There are two ways now to use the Docker images, depending on the overall scenario:
Start a standalone Mule ESB Enterprise instance
docker run -t -i --name='mule-ee-nodeX' mule-ee
Notice: On OSX boot2docker VBox requires port forwarding from docker -> VBox -> host (not even sure if this applies anymore...)
boot2docker ssh -L 8585:localhost:8585
FROM mule-ee:latest
.
.
ADD mule-app/target/mule-app-1.0.0-SNAPSHOT.zip /opt/mule-standalone-3.5.1/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 granthbr/mule-ee
Content type
Image
Digest
Size
501.1 MB
Last updated
about 6 years ago
docker pull granthbr/mule-ee