837eec064d
Cgroup resources are host dependent, they should be in hostConfig.
For backward compatibility, we just copy it to hostConfig, and leave it in
Config for now, so there is no regressions, but the right way to use this
throught json is to put it in HostConfig, like:
{
"Hostname": "",
...
"HostConfig": {
"CpuShares": 512,
"Memory": 314572800,
...
}
}
As we will add CpusetMems, CpusetCpus is definitely a better name, but some
users are already using Cpuset in their http APIs, we also make it compatible.
The main idea is keep using Cpuset in Config Struct, and make it has the same
value as CpusetCpus, but not always, some scenarios:
- Users use --cpuset in docker command, it can setup cpuset.cpus and can
get Cpuset field from docker inspect or other http API which will get
config info.
- Users use --cpuset-cpus in docker command, ditto.
- Users use Cpuset field in their http APIs, ditto.
- Users use CpusetCpus field in their http APIs, they won't get Cpuset field
in Config info, because by then, they should already know what happens
to Cpuset.
Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>
|
||
|---|---|---|
| .. | ||
| _static | ||
| docker-io_api.md | ||
| docker_io_accounts_api.md | ||
| docker_remote_api.md | ||
| docker_remote_api_v1.0.md | ||
| docker_remote_api_v1.1.md | ||
| docker_remote_api_v1.2.md | ||
| docker_remote_api_v1.3.md | ||
| docker_remote_api_v1.4.md | ||
| docker_remote_api_v1.5.md | ||
| docker_remote_api_v1.6.md | ||
| docker_remote_api_v1.7.md | ||
| docker_remote_api_v1.8.md | ||
| docker_remote_api_v1.9.md | ||
| docker_remote_api_v1.10.md | ||
| docker_remote_api_v1.11.md | ||
| docker_remote_api_v1.12.md | ||
| docker_remote_api_v1.13.md | ||
| docker_remote_api_v1.14.md | ||
| docker_remote_api_v1.15.md | ||
| docker_remote_api_v1.16.md | ||
| docker_remote_api_v1.17.md | ||
| docker_remote_api_v1.18.md | ||
| hub_registry_spec.md | ||
| README.md | ||
| registry_api.md | ||
| registry_api_client_libraries.md | ||
| remote_api_client_libraries.md | ||
This directory holds the authoritative specifications of APIs defined and implemented by Docker. Currently this includes:
- The remote API by which a docker node can be queried over HTTP
- The registry API by which a docker node can download and upload images for storage and sharing
- The index search API by which a docker node can search the public index for images to download
- The docker.io OAuth and accounts API which 3rd party services can use to access account information