I am planning to work on this.

Could someone add the Mesos integration tag?

When you say upgrade the dependency, as you implying that we will only support Docker 1.6+ going forward? I think we have quite a few users that are using older version of Docker on their systems that would still like to run kubernetes.

@roberthbailey As mentioned in the description, a major motivation is to use the new --cgroup-parent flag. I agree, there's no reason to break compatibility with older versions of Docker. The docker interface... interface already exposes a Version(), so we should be able to detect whether the intalled docker supports the new flags. @guenter, maybe this issue should be renamed to "Add support for new Docker 1.6 flags".

See: https://github.com/GoogleCloudPlatform/kubernetes/blob/fa4363d493551e0c27729e229fc35ea2790c186f/pkg/kubelet/dockertools/docker.go#L68

Thanks. Just want to make sure we aren't going to stop supporting older versions.

Which use of cgroup_parent do you intend? Just to put a box around all pods run by Kubernetes?

cc @vishh @vmarmol

See also #147 and #5980.

@bgrant0607 I think so, provided a top-level container (and a kubelet flag to set it) be a worthwhile first pass compatible with future plans. WDYT?

Our immediate goal are:

1. limit the total resource consumption of all containers that do not have any limits specified (batch),
2. limit system daemon resources usage.

Pod level resource isolation will land after that.

IIUC, what is required for Mesos is to configure kubelet to run itself and all the pods under a configurable cgroup hierarchy. That sounds fine.

@vishh @bgrant0607 cool, I think we're on the same page.

Pod limits is #168, btw.

Implemented by #7277