You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/11/18 23:40:12 UTC
[jira] [Updated] (YETUS-186) non-existent dockerfile should fail or
fallback
[ https://issues.apache.org/jira/browse/YETUS-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer updated YETUS-186:
-----------------------------------
Attachment: YETUS-186.00.patch
-00:
* make what we do on docker and dockerfile failure a bit more configurable. users can pick between any and all on continue, fallback, and fail. See the doc change for more info.
* re-arranged some of the docker initialization bits around
> non-existent dockerfile should fail or fallback
> -----------------------------------------------
>
> Key: YETUS-186
> URL: https://issues.apache.org/jira/browse/YETUS-186
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Blocker
> Attachments: YETUS-186.00.patch
>
>
> This is a long standing bug that I just now noticed. :( If the \-\-dockerfile param points to a file that doesn't actually exist, bad things happen. Which particular bad thing depends greatly upon what other images are already installed, but the vast majority end up with a stuck container at a bash prompt.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)