The Cargo Daemon is a Web-based application that uses the Cargo API to configure, start and stop containers on a remote machine.

The daemon is meant to be listening 24/7, to allow users to deploy new containers and web applications at their command.

It can be accessed using a browser-based UI, via Java API or Maven2 plugin.

Why use the Cargo Daemon?

Most web containers (e.g. Tomcat, Jetty) provide built-in remote deployment facilities already, also many of them already have daemon integrations; so why use the Cargo Daemon?

Table of Contents

The documentatation for the Cargo Daemon includes:


Cargo Daemon requires Java 6 or greater in order to run in standalone mode.

If you deploy the Cargo Daemon WAR file on an existing container, the minimum requirement is Java version 5.

To install and run the Cargo Daemon:

  1. Download the Cargo Daemon from the Downloads page
  2. Execute by typing:
java -jar target/cargo-daemon-webapp-<version>.war

where <version> is the version number of the daemon that you have downloaded.

By default, the Cargo Daemon will run on HTTP port 18000. To change it, use the -p option:

java -jar target/cargo-daemon-webapp-<version>.war -p 18001

Additionally, Cargo Daemon will save log files in the cargo home directory unless the -nologging option is used.

Note that the Cargo Daemon is a WAR file; you can actually also deploy it as a WAR on any existing container. This can be useful if you want to, for example, reuse a certain security configuration.


The daemon also accepts other parameters, in the form of system properties:

Property name



Default value


Directory in which the standaone daemon server stores its files. These include the temporary files (such as its own WAR and server temporary files) as well as the server log files (AWS-xxxxxxxxxxxxx.log, where xxxxxxxxxxxxx is the timestamp at which the deamon was started).

This property is not used and completely ignored if the daemon WAR file is deployed on an existing container.

(thumbs down)



Directory in which the daemon (be it standalone or deployed on an existing container) stores the list of containers, downloaded container archives, container logs, etc.

(thumbs down)


Note that the standalone daemon by default sets this to ${daemon.home}

Getting started using the browser UI

To use the Cargo Daemon via the browser UI, simply open http://<machine>:<port>/ -where <machine> is the machine host name or IP address and <port> is the port number used (default is 18000):

Getting started with the Java API / ANT tasks / Maven2/Maven3 plugin

As stated before, the Cargo Daemon is also available programmatically:


In order to connect to the Daemon via Java API or Maven2/Maven3 plugin, the minimum requirement is Java version 5.

To get the required libraries for using the Daemon via Java API, please check the Downloads page.