[
https://issues.apache.org/jira/browse/YETUS-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16795317#comment-16795317
]
Allen Wittenauer edited comment on YETUS-799 at 3/18/19 7:09 PM:
-----------------------------------------------------------------
This will likely fail jenkins since we can't test patches that make major
changes to the Docker code.
However, there are several full builds running with this patch:
Travis: https://travis-ci.org/aw-was-here/buretoolbox/builds/508036127
Gitlab: https://gitlab.com/_a__w_/buretoolbox/-/jobs/179785795
Circle: https://circleci.com/gh/aw-was-here/buretoolbox/621
was (Author: aw):
This will likely fail jenkins since we can't test patches that make major
changes to the Docker code.
However:
Travis: https://travis-ci.org/aw-was-here/buretoolbox/builds/508036127
Gitlab: https://gitlab.com/_a__w_/buretoolbox/-/jobs/179785795
Circle: https://circleci.com/gh/aw-was-here/buretoolbox/621
> Use real paths in docker container
> ----------------------------------
>
> Key: YETUS-799
> URL: https://issues.apache.org/jira/browse/YETUS-799
> Project: Yetus
> Issue Type: Improvement
> Components: Test Patch
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Major
> Attachments: YETUS-799.00.patch
>
>
> The --dockerind support doesn't really work for docker containers that need
> access to the file system because the paths inside the Yetus container are
> different than the ones that dockerd expects/the host uses externally. In
> order to fix this, we should just change our setup such that (minimally) the
> $BASEDIR inside the container is the same as the $BASEDIR outside the
> container and maximally, dump /testptch for almost everything and just use
> the same paths inside our container.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
