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

[jira] [Updated] (MESOS-6460) Mesos Support for Container Attach and Container Exec

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

Kevin Klues updated MESOS-6460:
-------------------------------
    Labels: debugging mesosphere  (was: )

> Mesos Support for Container Attach and Container Exec
> -----------------------------------------------------
>
>                 Key: MESOS-6460
>                 URL: https://issues.apache.org/jira/browse/MESOS-6460
>             Project: Mesos
>          Issue Type: Epic
>            Reporter: Kevin Klues
>            Assignee: Kevin Klues
>              Labels: debugging, mesosphere
>   Original Estimate: 840h
>  Remaining Estimate: 840h
>
> This Epic coordinates the design of new Agent APIs for attaching a remote client to the {{stdin}}, {{stdout}}, and {{stderr}} of a running Mesos task. It also outlines an API for launching new processes inside the same container as a running Mesos task and attaching to its {{stdin}}, {{stdout}}, and {{stderr}}. At a high level, these APIs mimic functionality similar to {{docker attach}} and {{docker exec}}.
> The primary motivation for such functionality is to enable users to debug their running Mesos tasks more easily. Specifically, these APIs will allow us to prod and probe the container of a running Mesos task by (for example) navigating its file system using an interactive {{bash}} shell or attaching {{gdb}} to any processes already running inside the container.



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