You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Justin Pinkul (JIRA)" <ji...@apache.org> on 2016/10/18 23:51:58 UTC
[jira] [Commented] (AURORA-1798) resolv.conf is not copied when
using the Mesos containerizer with a Docker image
[ https://issues.apache.org/jira/browse/AURORA-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15587070#comment-15587070 ]
Justin Pinkul commented on AURORA-1798:
---------------------------------------
Review: https://reviews.apache.org/r/53003/
> resolv.conf is not copied when using the Mesos containerizer with a Docker image
> --------------------------------------------------------------------------------
>
> Key: AURORA-1798
> URL: https://issues.apache.org/jira/browse/AURORA-1798
> Project: Aurora
> Issue Type: Bug
> Components: Executor
> Affects Versions: 0.16.0
> Reporter: Justin Pinkul
> Assignee: Justin Pinkul
>
> When Thermos launches a task using a Docker image it mounts the image as a volume and manually chroots into it. One consequence of this is the logic inside of the {{network/cni}} isolator that copies {{resolv.conf}} from the host into the new rootfs is bypassed. The Thermos executor should manually copy this file into the rootfs until Mesos pod support is implemented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)