You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2019/04/29 09:28:10 UTC

[jira] [Issue Comment Deleted] (MESOS-4137) Modularize plain-file logging for executor/task logs launched with the Docker Containerizer

     [ https://issues.apache.org/jira/browse/MESOS-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin updated MESOS-4137:
-------------------------
    Comment: was deleted

(was: www.rtat.net)

> Modularize plain-file logging for executor/task logs launched with the Docker Containerizer
> -------------------------------------------------------------------------------------------
>
>                 Key: MESOS-4137
>                 URL: https://issues.apache.org/jira/browse/MESOS-4137
>             Project: Mesos
>          Issue Type: Task
>          Components: docker, modules
>            Reporter: Joseph Wu
>            Assignee: Joseph Wu
>            Priority: Major
>              Labels: logging, mesosphere
>             Fix For: 0.27.0
>
>
> Adding a hook inside the Docker containerizer is slightly more involved than the Mesos containerizer.
> Docker executors/tasks perform plain-file logging in different places depending on whether the agent is in a Docker container itself
> || Agent || Code ||
> | Not in container | {{DockerContainerizerProcess::launchExecutorProcess}} |
> | In container | {{Docker::run}} in a {{mesos-docker-executor}} process |
> This means a {{ContainerLogger}} will need to be loaded or hooked into the {{mesos-docker-executor}}.  Or we will need to change how piping in done in {{mesos-docker-executor}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)