mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bhuvan Arumugam (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (MESOS-1524) Implement Docker support in Mesos
Date Sat, 21 Jun 2014 18:58:25 GMT

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

Bhuvan Arumugam edited comment on MESOS-1524 at 6/21/14 6:57 PM:
-----------------------------------------------------------------

{code}
Mounting the sandbox directory can be problematic if the path contains a colon, due to docker's
CLI parser.
{code}

This issue is fixed in {{0.18.0}}. The sandbox directory created with newer mesos slaves,
don't contain colon.

{code}
Docker doesn't actually pull an image if it exists in it's local cache. This is problematic
because if you update a tag on a docker registry (e.g a private one) a slave that has previously
launched an executor with that image won't download the new one... so you can get various
inconsistencies. The only way around this currently is to pull first.
{code}

[~tarnfeld] Docker can ignore local cache and pull from private or upstream registry when
using {{--no-cache}} option. With this flag, the image/tag will be pulled from registry even
though it was built in the same host earlier. I'm not saying it's the way to go, but it's
an option. This option is exposed to {{docker build}} command and hopefully it'll be exposed
in other commands like {{docker run}} soon.

{code}
--no-cache=false     Do not use cache when building the image
{code} 


was (Author: bhuvan):
{code}
Mounting the sandbox directory can be problematic if the path contains a colon, due to docker's
CLI parser.
{code}

This issue is fixed in {{0.18.0}}. The sandbox directory created with newer mesos slaves,
don't contain colon.

{code}
Docker doesn't actually pull an image if it exists in it's local cache. This is problematic
because if you update a tag on a docker registry (e.g a private one) a slave that has previously
launched an executor with that image won't download the new one... so you can get various
inconsistencies. The only way around this currently is to pull first.
{code}

[~tarnfeld] Docker can ignore local cache and pull from private or upstream registry when
using {{--no-cache}} option. With this flag, the image/tag will be pulled from registry even
though it was built in the same host earlier. I'm not saying it's the way to go, but it's
an option. This option is exposed to {{docker build}} command and hopefully it'll be exposed
in other commands like {{docker run}}.

{code}
--no-cache=false     Do not use cache when building the image
{code} 

> Implement Docker support in Mesos
> ---------------------------------
>
>                 Key: MESOS-1524
>                 URL: https://issues.apache.org/jira/browse/MESOS-1524
>             Project: Mesos
>          Issue Type: Epic
>            Reporter: Tobi Knaup
>            Assignee: Benjamin Hindman
>
> There have been two projects to add Docker support to Mesos, first via an executor, and
more recently via an external containerizer written in Python - Deimos: https://github.com/mesosphere/deimos
> We've got a lot of feedback from folks who use Docker and Mesos, and the main wish was
to make Docker a first class citizen in Mesos instead of a plugin that needs to be installed
separately. Mesos has been using Linux containers for a long time, first via LXC, then via
cgroups, and now also via the external containerizer. For a long time it wasn't clear what
the winning technology would be, but with Docker becoming the de-facto standard for handling
containers I think Mesos should make it a first class citizen and part of core.
> Let's use this JIRA to track wishes/feedback on the implementation.



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

Mime
View raw message