{section}
{column}

We provide a Docker image ready to launch a standalone Petals ESB container. It can be downloaded from [Docker hub|https://hub.docker.com/r/petals/petals-esb-container/].

h1. Launching the Petals ESB container

h2. Pre-requisites

It is assumed Docker is already installed on your machine.

{note}
By default, we publish all the Petals ESB container ports on the host system.

Be careful: ports used by Petals components are not exposed. As an example, if you deploy the SOAP BC, whose listening port is 8084, this port will not be reachable from the outside. In such a case, you should launch Petals with an additional option: *-p 8084:8084*. If you forgot the option, it is not possible with Docker to expose a port after the container was launched. So, you would have to kill the container and restart it.
{note}

h1. Working with Petals ESB container

h2. Connecting to Petals ESB

You can connect with usual tools: [Petals CLI|petalscomponents:Petals CLI SNAPSHOT] or [Petals Cockpit|petalscockpitsnapshot:], or you can also use basic tools as JConsole or VisualVM using the JMX URL: *{{service:jmx:rmi:///jndi/rmi://<docker-container-ip>:7700/PetalsJMX}}*, with {{petals/petals}} as credentials.

To get the IP adress of the Docker container, type in: *{{docker inspect petals | grep \"IPAddress\"}}*

h2. Getting Petals logs

Type in: *{{docker logs petals}}* to watch Petals logs.

h2. Introspecting the Docker container

Type in: *{{docker exec -ti petals /bin/bash}}*.
This will open a console in the container.

h2. Stopping and restarting Petals

Use *{{docker stop petals}}* to stop the container and *{{docker start petals}}* to relaunch it.

h1. Deleting the Docker container

Use *{{docker rm -f petals}}* to stop and delete the Docker container.

{column}
{column:width=35%}
{panel:title=Table of contents}{toc:outline=true}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list|showAnonymous=true|showCount=true|showLastTime=true}{panel}
{column}
{section}