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

Timothy Chen commented on MESOS-1747:
-------------------------------------

Hi [~dlaidlaw] thanks for the info, I've learned about this unfortunately after 
0.20.0 release and glad we are able to fix this.
It will be in the next release 0.20.1 which should be very soon (~1-2 weeks).

> Docker image parsing for private repositories
> ---------------------------------------------
>
>                 Key: MESOS-1747
>                 URL: https://issues.apache.org/jira/browse/MESOS-1747
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization, slave
>    Affects Versions: 0.20.0
>            Reporter: Don Laidlaw
>            Assignee: Timothy Chen
>              Labels: docker
>             Fix For: 0.20.1
>
>
> You cannot specify a port number for the host of a private docker repository. 
> Specified as follows: {noformat}
> "container": {
>     "type": "DOCKER",
>     "docker": {
>         "image": "docker-repo:5000/app-base:v0.1"
>     }
> }
> {noformat}
> results in an error:
> {noformat}
> Aug 29 14:33:29 ip-172-16-2-22 mesos-slave[1128]: E0829 14:33:29.487470  1153 
> slave.cpp:2484] Container '250e0479-552f-4e6f-81dd-71550e45adae' for executor 
> 't1-java.71d50bd1-2f89-11e4-ba9a-0adfe6b11716' of framework 
> '20140829-121838-184684716-5050-1177-0000' failed to start:Not expecting 
> multiple ':' in image: docker-repo:5000/app-base:v0.1
> {noformat}
> The message indicates only one colon character is allowed, but to supply a 
> port number for a private docker repository host you need to have two colons.
> Also if you use a '-' character in a host name you also get an error:
> {noformat}
> Invalid namespace name (docker-repo), only [a-z0-9_] are allowed, size 
> between 4 and 30
> {noformat}
> The hostname parts should not be limited to [a-z0-9_].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to