update api doc

Docker-DCO-1.1-Signed-off-by: Victor Vieux <vieux@docker.com> (github: vieux)
Upstream-commit: 6bb27f18d19201d8c0b3c509151935308c001c22
Component: engine
This commit is contained in:
Victor Vieux
2014-07-12 01:03:12 +00:00
parent c802db49a3
commit 76bdfebd46
3 changed files with 13 additions and 3 deletions
@@ -43,6 +43,12 @@ You can now use the `stop` parameter to stop running containers before removal
**New!**
You can now use the `kill` parameter to kill running containers before removal.
`POST /containers/(id)/start`
**New!**
The `hostConfig` option now accepts the field `CapAdd`, which specifies a list of capabilities
to add, and the field `CapDrop`, which specifies a list of capabilities to drop.
## v1.13
### Full Documentation
@@ -241,7 +241,9 @@ Return low-level information on the container `id`
]
},
"Links": ["/name:alias"],
"PublishAllPorts": false
"PublishAllPorts": false,
"CapAdd: ["NET_ADMIN"],
"CapDrop: ["MKNOD"]
}
}
@@ -410,7 +412,9 @@ Start the container `id`
"PublishAllPorts":false,
"Privileged":false,
"Dns": ["8.8.8.8"],
"VolumesFrom": ["parent", "other:ro"]
"VolumesFrom": ["parent", "other:ro"],
"CapAdd: ["NET_ADMIN"],
"CapDrop: ["MKNOD"]
}
**Example response**:
@@ -244,7 +244,7 @@ host as processes running outside containers on the host. Additional
information about running with `--privileged` is available on the
[Docker Blog](http://blog.docker.com/2013/09/docker-can-now-run-within-docker/).
In addition to `--privileged` the operator can have fine grain control over the
In addition to `--privileged`, the operator can have fine grain control over the
capabilities using `--cap-add` and `--cap-drop`. By default, Docker has a default
list of capabilities that are kept. Both flags support the value `all`, so if the
operator wants to have all capabilities but `MKNOD` they could use: