[
https://issues.apache.org/jira/browse/MESOS-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566131#comment-14566131
]
chenzongzhi commented on MESOS-2724:
------------------------------------
Yes, [~lins05] is right.
In my use case, I want different cgroups setting for different containers.
I have thought three way to implement my idea
1. from the docker side
Actually, docker will support all the cgroups setting, such as docker 1.7dev
version has supported the cfs_period_us setting, I think the btrfs setting will
add to docker in the future
2. from the mesos side
When we launch the docker container, we will limit the cgroups as the
MesosContainer, Certainly, the setting will overwrite the docker container's
setting. it is the user's own risk
3. from the outside
we can have a crontab in every machine, when we launch the task, we can change
the cgroups by add is to the crontab
I think change from the docker seem to be the simply way, but I don't know why
docker support these setting so slowly. In my opinion, adding other cgroups
setting is every easy, since docker had support some cgroups setting.
However, I think add a hook is also necessary, such as we will make directory
after launching the container. so the hook should be a script, not a setting.
It can be more flexibly.
> Support running custom commands on slaves when launcing a docker container
> --------------------------------------------------------------------------
>
> Key: MESOS-2724
> URL: https://issues.apache.org/jira/browse/MESOS-2724
> Project: Mesos
> Issue Type: Improvement
> Components: framework
> Reporter: chenzongzhi
> Assignee: Shuai Lin
>
> We use mesos + marathon to build our Paas platform. We meet a problem
> We want to execute some command after the docker container started. such as
> we want change the cgroup setting.
> We know We can execute some command in the docker container, but we want
> execute command in the host machine.
> Anyone know how to implement it or any good idea?
> Thanks
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
