[
https://issues.apache.org/jira/browse/MESOS-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210523#comment-15210523
]
Jie Yu commented on MESOS-3003:
-------------------------------
I'm closing this ticket because all the network related /etc/* files should be
handled by the network isolator because it (and only it) knows about the ip,
hostname information. Mounting in host /etc/* files blindly does not make sense.
> Support mounting in default configuration files/volumes into every new
> container
> --------------------------------------------------------------------------------
>
> Key: MESOS-3003
> URL: https://issues.apache.org/jira/browse/MESOS-3003
> Project: Mesos
> Issue Type: Improvement
> Components: containerization
> Reporter: Timothy Chen
> Assignee: Gilbert Song
> Labels: mesosphere, unified-containerizer-mvp
>
> Most container images leave out system configuration (e.g: /etc/*) and expect
> the container runtimes to mount in specific configurations as needed such as
> /etc/resolv.conf from the host into the container when needed.
> We need to support mounting in specific configuration files for command
> executor to work, and also allow the user to optionally define other
> configuration files to mount in as well via flags.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
