[
https://issues.apache.org/jira/browse/YETUS-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575525#comment-16575525
]
Jack Bearden commented on YETUS-657:
------------------------------------
The directory issue looks like a bug with the volume command. Mount seems to be
a better choice now since it actually checks the file before mounting.
{code:java}
In the case of bind mounts, the first field is the path to the file or
directory on the host machine.{code}
https://docs.docker.com/storage/bind-mounts/#choosing-the--v-or---mount-flag
> 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
>
> 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)
