There is a subtle inconsistency when running ash. This has to do with whether or not the --output-dir folder is specified on the command-line options.
When running outside of the container itself, if --output-dir is not specified, then a ash_output folder is created under the --source-dir folder.
However, when running ash from inside its own container (which is the recommended way to use it when running in a build automation environment), if --output-dir is not specified, then the folder is NOT created and output is placed in the --source-dir.
There is a subtle inconsistency when running
ash
. This has to do with whether or not the--output-dir
folder is specified on the command-line options.When running outside of the container itself, if
--output-dir
is not specified, then aash_output
folder is created under the--source-dir
folder.However, when running
ash
from inside its own container (which is the recommended way to use it when running in a build automation environment), if--output-dir
is not specified, then the folder is NOT created and output is placed in the--source-dir
.This behavior should be made to be consistent.