You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Creating containers with duplicated name used to return a 409 HTTP response, however, since 17.09 release it now returns a 400 response breaking compatibility for API users.
Steps to reproduce the issue:
Create a container docker create --name c1 busybox
Run curl -v -XPOST -H"Content-Type: application/json" -d'{"Image":"busybox"}' http://localhost:2375/containers/create?name=c1
Describe the results you received:
The HTTP response will be 400 Bad Request.
Describe the results you expected:
Prior to 17.09 the response would be 409 Conflict
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Client:
Version: 17.09.0-ce
API version: 1.32
Go version: go1.8.3
Git commit: afdb6d4
Built: Tue Sep 26 22:42:18 2017
OS/Arch: linux/amd64
Server:
Version: 17.09.0-ce
API version: 1.32 (minimum version 1.12)
Go version: go1.8.3
Git commit: afdb6d4
Built: Tue Sep 26 22:40:56 2017
OS/Arch: linux/amd64
Experimental: false
Description
Creating containers with duplicated name used to return a 409 HTTP response, however, since 17.09 release it now returns a 400 response breaking compatibility for API users.
Steps to reproduce the issue:
docker create --name c1 busybox
curl -v -XPOST -H"Content-Type: application/json" -d'{"Image":"busybox"}' http://localhost:2375/containers/create?name=c1
Describe the results you received:
The HTTP response will be 400 Bad Request.
Describe the results you expected:
Prior to 17.09 the response would be 409 Conflict
Additional information you deem important (e.g. issue happens only occasionally):
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
Virtualbox
The text was updated successfully, but these errors were encountered: