From c83888d19434b6969932b9752f7eb3d2c2330ab7 Mon Sep 17 00:00:00 2001 From: Doug Davis Date: Wed, 20 May 2015 14:51:58 -0700 Subject: [PATCH] Add a "Created" state for new containers that haven't been run yet Closes #13353 Signed-off-by: Doug Davis Upstream-commit: 835d319cc024a5c459ee32e83a9dd1acdbd3d9c6 Component: cli --- components/cli/docs/sources/reference/commandline/cli.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/components/cli/docs/sources/reference/commandline/cli.md b/components/cli/docs/sources/reference/commandline/cli.md index c4d012515c..770d2d3527 100644 --- a/components/cli/docs/sources/reference/commandline/cli.md +++ b/components/cli/docs/sources/reference/commandline/cli.md @@ -1033,7 +1033,8 @@ except the container is never started. You can then use the `docker start ` command to start the container at any point. This is useful when you want to set up a container configuration ahead of time -so that it is ready to start when you need it. +so that it is ready to start when you need it. The initial status of the +new container is `created`. Please see the [run command](#run) section and the [Docker run reference]( /reference/run/) for more details. @@ -1760,7 +1761,7 @@ The currently supported filters are: * label (`label=` or `label==`) * name (container's name) * exited (int - the code of exited containers. Only useful with `--all`) -* status (restarting|running|paused|exited) +* status (created|restarting|running|paused|exited) ##### Successfully exited containers