You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jake Farrell (JIRA)" <ji...@apache.org> on 2015/05/13 05:12:00 UTC

[jira] [Updated] (MESOS-2541) mesos containerizer should locally provide system files when chrooting

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

Jake Farrell updated MESOS-2541:
--------------------------------
    Issue Type: Bug  (was: Sub-task)
        Parent:     (was: MESOS-2540)

> mesos containerizer should locally provide system files when chrooting
> ----------------------------------------------------------------------
>
>                 Key: MESOS-2541
>                 URL: https://issues.apache.org/jira/browse/MESOS-2541
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization
>            Reporter: Jay Buffington
>
> When the mesos containerizer supports scheduler specified rootfs it should allow for system files to be locally specified.  Some files such as /etc/resolv.conf or perhaps /etc/hosts should be provided by the local system rather then the rootfs image specified by the scheduler.  When the image is built, it is unknown where it will be deployed.   We want the /etc/resolv.conf to specify local resolvers rather than forcing to choose a random resolvers at build time.
> I propose that the mesos-slave always trump an /etc/resolv.conf provided by the scheduler in an image, but running tasks should be able to modify these files (this was an issue with docker[1])
> [1] https://github.com/docker/docker/issues/2267



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