heya @kenshin54

can you please update the cli.rst document with the new cgroup command, and the api docs too?

Also: (stolen from @crosbymichael)

We just began requiring contributors to sign their commits following these rules: https://github.com/dotcloud/docker/blob/master/CONTRIBUTING.md#sign-your-work

Each commit in your PR must be signed in the following format:
Docker-DCO-1.1-Signed-off-by: Joe Smith <[email protected]> (github: github_handle)

Please rebase and sign each commit.

@SvenDowideit OK, I will update document and sign the commits later.

Hi @SvenDowideit

I have added the documentation and signed the commit. Please check it out.

ping @crosbymichael

@kenshin54 you seem to have not signed commit 258c9ec :)

docs LGTM tho - I like more prose, but don't worry, we can add that if its needed :)

This seems leaky to me as we probably shouldn't expose cgroups via the API for portability. @shykes @crosbymichael - thoughts. We probably actually want a resource/constraint API.

Ignoring the API design - please note we already have a cgroups package please use that rather than a new top level cgroups.go

Yeah exposing cgroups directly is too low-level, because that API is not stable across versions and distros of linux . We would be stuck with clients depending on different variations.

As a start, how about exposing a dynamic version of the 2 cgroup-related options we already support: -m and -c ?

For example the syntax could be: docker set = where could be "memory" or "cpu"?

I am going to close this PR for now. Maybe we can open an issue if you are still wanting to implement this. Alot has changed since this PR was opened so it would probably be better to start fresh after we discuss design.

Thanks.