-
Notifications
You must be signed in to change notification settings - Fork 18.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Return "invalid parameter" when linking to non-existing container #39852
Return "invalid parameter" when linking to non-existing container #39852
Conversation
12ddad2
to
cf470e9
Compare
cf470e9
to
2c3e001
Compare
Only failure is a flaky test (tracked through #38521)
|
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>
2c3e001
to
422067b
Compare
ping @tiborvass @cpuguy83 PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Failure on RS1 is https://ci.docker.com/public/job/moby/job/PR-39852/5/execution/node/180/log/ which is known to be flaky (#36801), and for which I have a PR to skip it conditionally; #39856
Everything else is green, so I'll go ahead and merge this one |
fixes #39823
fixes docker/for-mac#3871
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.