[jira] [Updated] (MESOS-1684) Default the System .dockercfg if present

["Timothy Chen (JIRA)" <ji...@apache.org>]

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

Timothy Chen updated MESOS-1684:
--------------------------------
    Component/s: docker

> Default the System .dockercfg if present
> ----------------------------------------
>
>                 Key: MESOS-1684
>                 URL: https://issues.apache.org/jira/browse/MESOS-1684
>             Project: Mesos
>          Issue Type: Improvement
>          Components: containerization, docker
>    Affects Versions: 0.20.0
>         Environment: General Linux with Docker Support
>            Reporter: Ken Sipe
>
> The behavior of the up coming mesos release 0.20 with docker support is to set the sandbox to the $HOME.  This is great if .dockercfg is one of the payloads of the URIs.     This solves an important model.  However the other model is that docker and login information is provisioned on all the slaves.   The configuration file has sensitive credential information which is just Base64 encoded.  It is likely that many organizations will not want pass that around via URIs and will want to provision the slaves with this file.
> I suggest that if we know the task is docker (dockerinfo is provided), then we check to see if $HOME/.dockercfg exists.  if it does, copy that first as a default.   If it exists and a .dockercfg is passed, the extraction will copy over the default file.
> This has the advantage of providing a default consistent with what is expect in the docker world + the ability to override to allow each framework or task to define its own private repo.



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