Sebastiaan van Stijn 1e0234ddc6 Return "invalid parameter" when linking to non-existing container ... Trying to link to a non-existing container is not valid, and should return an "invalid parameter" (400) error. Returning a "not found" error in this situation would make the client report the container's image could not be found. Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit 422067ba7b) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>		2019-09-10 23:57:45 +02:00
..
build	Builder: fix "COPY --from" to non-existing directory on Windows	2019-08-08 17:05:11 +02:00
config	Add test for keeping same daemon ID on upgrade	2019-06-18 18:55:00 +00:00
container	Return "invalid parameter" when linking to non-existing container	2019-09-10 23:57:45 +02:00
image	Skip TestImagesFilterMultiReference on API < v1.40	2019-05-13 15:26:22 -07:00
internal	Enable integrations API tests for Windows CI	2019-06-12 10:16:04 +02:00
network	Skip TestServiceRemoveKeepsIngressNetwork	2019-09-07 01:09:38 +02:00
plugin	Improvements to the test runners	2019-08-19 18:55:57 +02:00
secret	Fatalf -> Fatal	2019-01-27 00:43:24 +00:00
service	Gracefully take care of the error case when a container	2019-06-12 20:00:51 +02:00
session	Testing: create new daemon (only) if needed	2019-02-23 13:32:59 +01:00
system	Revert "Remove Schema1 integration test suite"	2019-06-18 18:54:45 +00:00
testdata/https	integration/plugin/authz: port tests from integration-cli	2017-10-02 14:20:59 +01:00
volume	Enable integrations API tests for Windows CI	2019-06-12 10:16:04 +02:00
doc.go	Add canonical import comment	2018-02-05 16:51:57 -05:00