[
https://issues.apache.org/jira/browse/MESOS-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418424#comment-15418424
]
Qian Zhang commented on MESOS-5991:
-----------------------------------
After I run the first unified container, in {{cpu}}, {{cpuacct}}, {{freezer}},
{{memory}} subsystems, there will be a new sub-directory whose name is the ID
of the unified container, and in each subsystem, there will be a new
sub-directory whose name is the ID of that "busybox" Docker container, like
this:
{code}
...
├── memory
│ ├── docker
│ │ ├── 563c509b218162089936a68032212b34ef3a6e24a9a6605a1de4c928326ea228
│ ├── mesos
│ │ └── 2c28749a-0942-4907-95bc-78967b92a518
...
{code}
After I run the second unified container, the same will happen again, like this:
{code}
...
├── memory
│ ├── docker
│ │ ├── 447f4233751a35249d63db4b42c21d288336ed08180f2b4d2d1ef0b139768b5f
│ │ ├── 563c509b218162089936a68032212b34ef3a6e24a9a6605a1de4c928326ea228
│ ├── mesos
│ │ ├── 2c28749a-0942-4907-95bc-78967b92a518
│ │ └── 48b2a1ff-0cc6-454c-810f-568b04bcc1a7
...
{code}
It seems working fine. The only issue I can see is, when I terminate the
unified container (e.g., I can trigger this by killing "mesos-execute") while
the "busybox" Docker container is still running in it, then the corresponding
sub-directory under "mesos" will be removed which is good, but the
corresponding sub-directory under "docker" will NOT be removed, that's because
there is no chance for the Docker daemon running in the unified container to
clean it up since the unified container has been terminated.
BTW, I have everything running on a single Ubuntu 14.04 VM.
> Support running docker daemon inside a container using unified containerizer.
> -----------------------------------------------------------------------------
>
> Key: MESOS-5991
> URL: https://issues.apache.org/jira/browse/MESOS-5991
> Project: Mesos
> Issue Type: Epic
> Reporter: Jie Yu
>
> The goal is to develop necessary pieces in unified containerizer so that
> framework can launch a full fledge docker daemon in a container.
> This will be useful for frameworks like jenkins. The jenkins job can still
> use docker cli to do build (e.g., `docker build`, `docker push`), but we
> don't have to install docker daemon on the host anymore.
> Looks like LXD already support that and is pretty stable for some users. We
> should do some investigation to see what features that's missing in unified
> containerizer to be able to match what lxd has. Will track all the
> dependencies in this ticket.
> https://www.stgraber.org/2016/04/13/lxd-2-0-docker-in-lxd-712/
> Cgroups and user namespaces support are definitely missing pieces.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
