You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Shuai Lin (JIRA)" <ji...@apache.org> on 2016/02/23 07:31:18 UTC

[jira] [Commented] (MESOS-4743) Mesos fetcher not working correctly on docker apps on CoreOS

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

Shuai Lin commented on MESOS-4743:
----------------------------------

Is your mesos slave running inside a container itself? If so it may be related to [MESOS-4249].

> Mesos fetcher not working correctly on docker apps on CoreOS
> ------------------------------------------------------------
>
>                 Key: MESOS-4743
>                 URL: https://issues.apache.org/jira/browse/MESOS-4743
>             Project: Mesos
>          Issue Type: Bug
>          Components: docker, fetcher
>    Affects Versions: 0.26.0
>            Reporter: Guillermo Rodriguez
>
> I initially sent this issue to the Marathon group. They asked me to send it here. This is the original thread:
> https://github.com/mesosphere/marathon/issues/3179
> Then they closed it so I had to ask again with more proof.
> https://github.com/mesosphere/marathon/issues/3213
> In a nutshell, when I start a Marathon task that uses the URI while running on CoreOS. The file is effectively fetched but not passed to the container. I can see the file in the mesos UI but the file is not in the container. It is, however, downloaded to another folder.
> It is very simple to test. The original ticket has two files attaches with a Marathon JSON for a Prometheus server and a prometheus.yml config file. The objective is to start prometheus with the config file.
> CoreOS 899.6
> Mesos 0.26
> Marathon 0.15.2
> Thanks!



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