[
https://issues.apache.org/jira/browse/YETUS-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated YETUS-657:
-----------------------------------
Flags: Important
Release Note:
<!-- markdown -->
In addition to fixing issues with Docker containers not creating certain
reports if the files didn't previous exist, the brief report mode has had some
internal and external code cleanup to make it consistent. As a result, two
options have been renamed:
* The --brief-report-file option is now --brief-text-file
* The --brief-report-long option is now --brief-text-long
Users will need to change their command lines as appropriate.
> volumes on non-existent files creates a directory
> -------------------------------------------------
>
> Key: YETUS-657
> URL: https://issues.apache.org/jira/browse/YETUS-657
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
> Affects Versions: 0.8.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Blocker
> Fix For: 0.8.0
>
> Attachments: YETUS-657.00.patch
>
>
> It would appear that at some point docker's behavior has changed with regards
> to volumes and non-existent files.
> When running docker -v file:file:
> In 17.05 (ASF Jenkins), this creates a file and good to go.
> In 17.12 and 18.05, this creates a directory.
> In order to make this safe, there are multiple routes that could be
> approached:
> a) only mount directories
> b) make sure the file exists before the volume mount
> In all instances, the -v params for docker need to get audited to make sure
> things are working as expected. In particular, some of the reporting is
> known to be broken, thus making this a blocking bug.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
