{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.
h2. Downloading the Docker image of Petals ESB container
Type in the following command: *{{docker pull petals/petals-esb-container:5.1.0}}*
h1. Starting Petals ESB
Type in: *{{docker run -d -p 7700:7700 -p 7800:7800 --name petals petals/petals-esb-container:5.1.0}}*
You can verify the container works with *{{docker ps}}*
{tip}By default, we publish all the Petals ports on the host system.
Be careful: ports used by provider 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 8080:8080*. 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.{tip}
h1. Connecting to Petals ESB
You can connect with usual tools: [Petals CLI|petalscomponents:Petals CLI 3.0.0+] or Petals Cockpit
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.
h1. Getting Petals logs
Type in *docker logs petals* to watch Petals logs.
h1. Introspecting the container
Type in *docker exec -ti petals /bin/bash*.
This will open a console in the container.
h1. Stopping Petals
Use *docker stop petals* to stop the container and *docker start petals* to relaunch it.
h1. Deleting the container
Use *docker rm -f petals* to stop and delete the 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}
{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.
h2. Downloading the Docker image of Petals ESB container
Type in the following command: *{{docker pull petals/petals-esb-container:5.1.0}}*
h1. Starting Petals ESB
Type in: *{{docker run -d -p 7700:7700 -p 7800:7800 --name petals petals/petals-esb-container:5.1.0}}*
You can verify the container works with *{{docker ps}}*
{tip}By default, we publish all the Petals ports on the host system.
Be careful: ports used by provider 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 8080:8080*. 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.{tip}
h1. Connecting to Petals ESB
You can connect with usual tools: [Petals CLI|petalscomponents:Petals CLI 3.0.0+] or Petals Cockpit
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.
h1. Getting Petals logs
Type in *docker logs petals* to watch Petals logs.
h1. Introspecting the container
Type in *docker exec -ti petals /bin/bash*.
This will open a console in the container.
h1. Stopping Petals
Use *docker stop petals* to stop the container and *docker start petals* to relaunch it.
h1. Deleting the container
Use *docker rm -f petals* to stop and delete the 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}