[ 
https://issues.apache.org/jira/browse/MESOS-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julien Eid updated MESOS-1691:
------------------------------

    Description: 
I know this is pretty minor but is a bit confusing for people new to using the 
Docker containerizer. The error message for a malformed Docker image URL is "No 
docker image found, skipping launch", which was pretty confusing to me as I had 
kept specifying the image and it was saying there was none instead of telling 
me the string was wrong. I think it would be better if it was "Incorrect Docker 
image specified, Docker image URL's must start with docker:///"

I wouldn't mind working on this issue.

  was:
I know this is pretty minor but is a bit confusing for people new to using the 
Docker containerizer. The error message for a malformed Docker image URL is "No 
docker image found, skipping launch", which was pretty confusing to me as I had 
kept specifying the image and it was saying there was none instead of telling 
me the string was wrong.

I think it would be better if it was "Incorrect Docker image specified, Docker 
image URL's must start with docker:///"


> Improvement of Docker image location failure message
> ----------------------------------------------------
>
>                 Key: MESOS-1691
>                 URL: https://issues.apache.org/jira/browse/MESOS-1691
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Julien Eid
>            Priority: Trivial
>
> I know this is pretty minor but is a bit confusing for people new to using 
> the Docker containerizer. The error message for a malformed Docker image URL 
> is "No docker image found, skipping launch", which was pretty confusing to me 
> as I had kept specifying the image and it was saying there was none instead 
> of telling me the string was wrong. I think it would be better if it was 
> "Incorrect Docker image specified, Docker image URL's must start with 
> docker:///"
> I wouldn't mind working on this issue.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to