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 06:56:11 UTC

[jira] [Commented] (YETUS-186) non-existent dockerfile should fail or fallback

    [ https://issues.apache.org/jira/browse/YETUS-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010302#comment-15010302 ] 

Allen Wittenauer commented on YETUS-186:
----------------------------------------

We have a few options here:
* fail
* don't spawn docker
* spawn docker, but use our image instead

I think failing and reporting it back up the chain is the correct thing to do since if docker is being invoked, there is a good chance the whole build would have failed anyway.

> 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
>            Priority: Blocker
>
> 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)