We're updating the issue view to help you get more done. 

Standalone configurations with no home set should default to the same tmp directory

Description

This was the behavior of cargo 0.7 but was changed in Cargo 0.8 and I believe we need to revert it.

The issue is that when you start a container and you don't specify a home directory for the standalone config, cargo automatically computes a default directory in java.io.tmpdir. However it picks a different directory every time. Thus when the container has to be stopped it tries to stop it but from a different configuration directory.

Status

Assignee

Vincent Massol

Reporter

Vincent Massol

Components

Fix versions

Affects versions

0.8

Priority

Major