[
https://issues.apache.org/jira/browse/MESOS-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317647#comment-14317647
]
Ian Downes commented on MESOS-2349:
-----------------------------------
1. For operators to enter the container to run debug tooling, e.g., tcpdump or
netstat when using the port_mapping isolator, directly when on the host.
2. To use as a force command (or otherwise) for ssh to put a user inside the
container. E.g., Aurora has "aurora ssh" which currently will ssh to the host
and chdir to the sandbox under the executor work directory.
> Provide a way to execute an arbitrary process in a MesosContainerizer
> container context
> ---------------------------------------------------------------------------------------
>
> Key: MESOS-2349
> URL: https://issues.apache.org/jira/browse/MESOS-2349
> Project: Mesos
> Issue Type: Improvement
> Components: isolation
> Affects Versions: 0.22.0, 0.21.1
> Reporter: Ian Downes
>
> Include a separate binary that when provided with a container_id, path to an
> executable, and optional arguments will find the container context, enter it,
> and exec the executable.
> e.g.,
> {noformat}
> mesos-container-exec --container_id=abc123 [--] /path/to/executable [arg1 ...]
> {noformat}
> This need only support (initially) containers created with the
> MesosContainerizer and will support all isolators shipped with Mesos, i.e.,
> it should find and enter the cgroups and namespaces for the running executor
> of the specified container.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
