Docker
Since Camel 2.15
Both producer and consumer are supported
Camel component for communicating with Docker.
The Docker Camel component leverages the docker-java via the Docker Remote API.
URI format
docker://[operation]?[options]Where operation is the specific action to perform on Docker.
General Options
The Docker component supports 21 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
configuration (common) |
To use the shared docker configuration |
DockerConfiguration |
|
email (common) |
Email address associated with the user |
String |
|
host (common) |
Required Docker host |
localhost |
String |
port (common) |
Docker port |
2375 |
Integer |
requestTimeout (common) |
Request timeout for response (in seconds) |
Integer |
|
bridgeErrorHandler (consumer) |
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
boolean |
lazyStartProducer (producer) |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
boolean |
autowiredEnabled (advanced) |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
boolean |
cmdExecFactory (advanced) |
The fully qualified class name of the DockerCmdExecFactory implementation to use |
com.github.dockerjava.netty.NettyDockerCmdExecFactory |
String |
followRedirectFilter (advanced) |
Whether to follow redirect filter |
false |
boolean |
loggingFilter (advanced) |
Whether to use logging filter |
false |
boolean |
maxPerRouteConnections (advanced) |
Maximum route connections |
100 |
Integer |
maxTotalConnections (advanced) |
Maximum total connections |
100 |
Integer |
parameters (advanced) |
Additional configuration parameters as key/value pairs |
Map |
|
serverAddress (advanced) |
Server address for docker registry. |
String |
|
socket (advanced) |
Socket connection mode |
true |
boolean |
certPath (security) |
Location containing the SSL certificate chain |
String |
|
password (security) |
Password to authenticate with |
String |
|
secure (security) |
Use HTTPS communication |
false |
boolean |
tlsVerify (security) |
Check TLS |
false |
boolean |
username (security) |
User name to authenticate with |
String |
The Docker endpoint is configured using URI syntax:
docker:operation
with the following path and query parameters:
Path Parameters (1 parameters):
| Name | Description | Default | Type |
|---|---|---|---|
operation |
Required Which operation to use. There are 31 enums and the value can be one of: events, stats, auth, info, ping, version, imagebuild, imagecreate, imageinspect, imagelist, imagepull, imagepushimageremove, imagesearch, imagetag, containerattach, containercommit, containercopyfile, containercreate, containerdiffinspectcontainer, containerkill, containerlist, containerlog, containerpause, containerrestart, containerremove, containerstartcontainerstop, containertop, containerunpause, containerwait, execcreate, execstart |
DockerOperation |
Query Parameters (22 parameters):
| Name | Description | Default | Type |
|---|---|---|---|
email (common) |
Email address associated with the user |
String |
|
host (common) |
Required Docker host |
localhost |
String |
port (common) |
Docker port |
2375 |
Integer |
requestTimeout (common) |
Request timeout for response (in seconds) |
Integer |
|
bridgeErrorHandler (consumer) |
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
boolean |
exceptionHandler (consumer) |
To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
ExceptionHandler |
|
exchangePattern (consumer) |
Sets the exchange pattern when the consumer creates an exchange. There are 3 enums and the value can be one of: InOnly, InOut, InOptionalOut |
ExchangePattern |
|
lazyStartProducer (producer) |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
boolean |
cmdExecFactory (advanced) |
The fully qualified class name of the DockerCmdExecFactory implementation to use |
com.github.dockerjava.netty.NettyDockerCmdExecFactory |
String |
followRedirectFilter (advanced) |
Whether to follow redirect filter |
false |
boolean |
loggingFilter (advanced) |
Whether to use logging filter |
false |
boolean |
maxPerRouteConnections (advanced) |
Maximum route connections |
100 |
Integer |
maxTotalConnections (advanced) |
Maximum total connections |
100 |
Integer |
parameters (advanced) |
Additional configuration parameters as key/value pairs |
Map |
|
serverAddress (advanced) |
Server address for docker registry. |
String |
|
socket (advanced) |
Socket connection mode |
true |
boolean |
synchronous (advanced) |
Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). |
false |
boolean |
certPath (security) |
Location containing the SSL certificate chain |
String |
|
password (security) |
Password to authenticate with |
String |
|
secure (security) |
Use HTTPS communication |
false |
boolean |
tlsVerify (security) |
Check TLS |
false |
boolean |
username (security) |
User name to authenticate with |
String |
Header Strategy
All URI option can be passed as Header properties. Values found in a message header take precedence over URI parameters. A header property takes the form of a URI option prefixed with CamelDocker as shown below
| URI Option | Header Property |
|---|---|
containerId |
CamelDockerContainerId |
Examples
The following example consumes events from Docker:
from("docker://events?host=192.168.59.103&port=2375").to("log:event");The following example queries Docker for system wide information
from("docker://info?host=192.168.59.103&port=2375").to("log:info");Dependencies
To use Docker in your Camel routes you need to add a dependency on camel-docker, which implements the component.
If you use Maven you can just add the following to your pom.xml, substituting the version number for the latest and greatest release (see the download page for the latest versions).
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-docker</artifactId>
<version>x.x.x</version>
</dependency>Spring Boot Auto-Configuration
When using docker with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
<dependency>
<groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-docker-starter</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>The component supports 22 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
camel.component.docker.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.docker.bridge-error-handler |
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
Boolean |
camel.component.docker.cert-path |
Location containing the SSL certificate chain |
String |
|
camel.component.docker.cmd-exec-factory |
The fully qualified class name of the DockerCmdExecFactory implementation to use |
com.github.dockerjava.netty.NettyDockerCmdExecFactory |
String |
camel.component.docker.configuration |
To use the shared docker configuration. The option is a org.apache.camel.component.docker.DockerConfiguration type. |
DockerConfiguration |
|
camel.component.docker.email |
Email address associated with the user |
String |
|
camel.component.docker.enabled |
Whether to enable auto configuration of the docker component. This is enabled by default. |
Boolean |
|
camel.component.docker.follow-redirect-filter |
Whether to follow redirect filter |
false |
Boolean |
camel.component.docker.host |
Docker host |
localhost |
String |
camel.component.docker.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.docker.logging-filter |
Whether to use logging filter |
false |
Boolean |
camel.component.docker.max-per-route-connections |
Maximum route connections |
100 |
Integer |
camel.component.docker.max-total-connections |
Maximum total connections |
100 |
Integer |
camel.component.docker.parameters |
Additional configuration parameters as key/value pairs |
Map |
|
camel.component.docker.password |
Password to authenticate with |
String |
|
camel.component.docker.port |
Docker port |
2375 |
Integer |
camel.component.docker.request-timeout |
Request timeout for response (in seconds) |
Integer |
|
camel.component.docker.secure |
Use HTTPS communication |
false |
Boolean |
camel.component.docker.server-address |
Server address for docker registry. |
String |
|
camel.component.docker.socket |
Socket connection mode |
true |
Boolean |
camel.component.docker.tls-verify |
Check TLS |
false |
Boolean |
camel.component.docker.username |
User name to authenticate with |
String |