Timeout after which the container start/stop is deemed failed
This feature is only available for local containers
Cargo has a timeout for container start and stop operations. If the time taken to start/stop a container exceeds the timeout period the operations is considered failed and the container is then set in the unknown state.
The default timeout value is 2 minutes (120000 milliseconds). This value can be modified as shown below.
If the given timeout is to small, cargo/maven will give you an error message similar to this:
Example using the Java API
Example using the Maven 2 plugin
As of CARGO version 1.0.2, if you set the timeout to 0, CARGO will not wait for the container to start or stop.