[
https://issues.apache.org/jira/browse/MESOS-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631753#comment-14631753
]
Jie Yu commented on MESOS-3003:
-------------------------------
Do you guys have any design on this yet (e.g., what flags are you going to
create)?
Also, are you going to retire --default_container_info flag because the
framework might just specify the container info and you still need to append
some volumes from the host? Also, there some other issues related to
default_container_info which hasn't been resolved yet:
https://issues.apache.org/jira/browse/MESOS-2463
https://reviews.apache.org/r/25549/
> 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
> Labels: mesosphere
>
> 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)
