The Docker executor maybe could support soft/hard resource limit to enable more flexible resources sharing among the applications.
|hard limit||--cpu-period & --cpu-quota||--memory & --memory-swap|
And now the task protobuf message has only one resource struct that used to describe the cgroup limit, and the docker executor handle is like the following, only --memory and --cpu-shares were set:
I hope that the executor and the protobuf message could separate the resource to the two parts: soft and hard. Then the user could set 2 levels resource limits for the docker.