Sebastiaan van Stijn c76331e13f api/types/container: put "valid" field as first check in tests ...

Make if more explicit which test-cases should be valid, and make it the
first field, because the "valid" field is shared among all test-cases in
the test-table, and making it the first field makes it slightly easier
to distinguish valid from invalid cases.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

2023-03-15 18:49:14 +01:00

..

config.go

container/exec: Support ConsoleSize

2022-06-24 11:54:25 +02:00

container_changes.go

api/types: re-generate with new template

2019-11-05 11:32:41 -08:00

container_top.go

swagger: reformat, and wrap to ~80-chars

2020-05-02 18:10:28 +02:00

container_update.go

api/types: re-generate with new template

2019-11-05 11:32:41 -08:00

create_response.go

api: rename container.ContainerCreateCreatedBody to container.CreateResponse

2022-04-28 22:39:18 +02:00

hostconfig_unix_test.go

api/types/container: put "valid" field as first check in tests

2023-03-15 18:49:14 +01:00

hostconfig_unix.go

Update to Go 1.17.0, and gofmt with Go 1.17

2021-08-24 23:33:27 +02:00

hostconfig_windows.go

Add canonical import comment

2018-02-05 16:51:57 -05:00

hostconfig.go

daemon: add annotations to container HostConfig

2023-02-23 18:59:00 -05:00

wait_exit_error.go

api: rename ContainerWaitOKBody to container.WaitResponse

2022-04-28 22:38:20 +02:00

wait_response.go

api: swagger: adjust ContainerWaitResponse error as optional

2022-05-30 16:42:12 +01:00

waitcondition.go

Add canonical import comment

2018-02-05 16:51:57 -05:00