aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua Cohen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1798) resolv.conf is not copied when using the Mesos containerizer with a Docker image
Date Thu, 20 Oct 2016 18:01:58 GMT

    [ https://issues.apache.org/jira/browse/AURORA-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15592520#comment-15592520
] 

Joshua Cohen commented on AURORA-1798:
--------------------------------------

I unset the fix version, we set these explicitly when we cut a new release.

> 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)

Mime
View raw message