IPAM Driver name shouldn't be required in network create #25735
Description
I'm opening an issue here as well as on engine-api: docker-archive-public/docker.engine-api#368
There seems to be a disagreement between engine-api and docker about whether the IPAM driver name is required in the network create api. engine-api doesn't set it by default and docker requires it by default. This breaks existing applications that use engine-api to create overlay networks.
Output of docker version:
Client:
Version: 1.12.0
API version: 1.24
Go version: go1.6.3
Git commit: 8eab29e
Built: Thu Jul 28 21:04:48 2016
OS/Arch: linux/amd64
Experimental: true
Server:
Version: 1.12.0
API version: 1.24
Go version: go1.6.3
Git commit: 8eab29e
Built: Thu Jul 28 21:04:48 2016
OS/Arch: linux/amd64
Experimental: true
Output of docker info:
Containers: 153
Running: 13
Paused: 0
Stopped: 140
Images: 743
Server Version: 1.12.0
Storage Driver: overlay2
Backing Filesystem: extfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: overlay host null bridge
Swarm: active
NodeID: 0jnlg1wjfbomj3vpagxqcjied
Is Manager: true
ClusterID: 7npas0qe6x670sbnzawyulo5y
Managers: 1
Nodes: 1
Orchestration:
Task History Retention Limit: 10
Raft:
Snapshot interval: 10000
Heartbeat tick: 1
Election tick: 3
Dispatcher:
Heartbeat period: 5 seconds
CA configuration:
Expiry duration: 3 months
Node Address: 172.17.0.1
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Kernel Version: 4.6.4-1-ARCH
Operating System: Arch Linux
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.709 GiB
Name: compooter
ID: GKSI:YHZC:YPNI:PAGO:EYPD:AYME:K6BY:BAIH:EBKQ:SOAK:WUFP:6MJM
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 1966
Goroutines: 1943
System Time: 2016-08-15T15:22:58.960604046-07:00
EventsListeners: 2
Username: viktorstanchev
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
172.17.0.1
192.168.0.106
dtr2-2061409770.us-west-2.elb.amazonaws.com
new-1428125395.us-west-2.elb.amazonaws.com
127.0.0.0/8
Additional environment details (AWS, VirtualBox, physical, etc.):
Steps to reproduce the issue:
Describe the results you received:
error
Describe the results you expected:
no error
Additional information you deem important (e.g. issue happens only occasionally):