docker/container
Sebastiaan van Stijn b654b6244d
Improve description of Running and Paused booleans
Commit abd72d4008 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>
2017-05-19 12:29:54 +02:00
..
stream Update ContainerWait API 2017-05-16 15:11:39 -07:00
archive.go
container.go Adding network specific options to service create/update 2017-05-17 18:46:34 -07:00
container_linux.go
container_notlinux.go support custom paths for secrets 2017-05-10 10:23:07 -07:00
container_unit_test.go support custom paths for secrets 2017-05-10 10:23:07 -07:00
container_unix.go Add config support to executor backend 2017-05-11 10:08:21 -07:00
container_windows.go Add Windows configs support 2017-05-16 14:25:32 -07:00
env.go
env_test.go
health.go
history.go
memory_store.go
memory_store_test.go
monitor.go
mounts_unix.go
mounts_windows.go
state.go Improve description of Running and Paused booleans 2017-05-19 12:29:54 +02:00
state_solaris.go
state_test.go Update ContainerWait API 2017-05-16 15:11:39 -07:00
state_unix.go
state_windows.go
store.go