Sebastiaan van Stijn 4bffda81c9 Improve description of Running and Paused booleans ...

Commit abd72d4008dde7ee8249170d49eb4bc963c51e24 added
a "FIXME" comment to the container "State", mentioning
that a container cannot be both "Running" and "Paused".

This comment was incorrect, because containers on
Linux actually _must_ be running in order to be
paused.

This patch adds additional information both in a
comment, and in the API documentation to clarify
that these booleans are not mutually exclusive.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Upstream-commit: b654b6244d6d63a0758029488a95feb446e089bd
Component: engine

2017-05-19 12:29:54 +02:00

..

stream

…

archive.go

…

container_linux.go

…

container_notlinux.go

…

container_unit_test.go

…

container_unix.go

…

container_windows.go

…

container.go

…

env_test.go

…

env.go

…

health.go

…

history.go

…

memory_store_test.go

…

memory_store.go

…

monitor.go

…

mounts_unix.go

…

mounts_windows.go

…

state_solaris.go

…

state_test.go

…

state_unix.go

…

state_windows.go

…

state.go

Improve description of Running and Paused booleans

2017-05-19 12:29:54 +02:00

store.go

…