[IPVLAN] Interface being put in promiscuous mode unnecessarily

[FlorinAsavoaie]

Long story short, when using ipvlan, even if the libcontainerd and even the Kernel documentation says that it doesn't need the network to be in promiscuous mode (since it is using a single MAC), apparently it still does.

Steps to reproduce the issue:

1. Create a new L2 ipvlan network: docker network create -d ipvlan ...
2. Start a container attached to that network: docker run -ti --rm --network MyNetwork ubuntu /bin/bash

Describe the results you received:
Kernel logs: "device ens160 entered promiscuous mode".

Describe the results you expected:
It should NOT enter promiscuous mode.

Additional information you deem important (e.g. issue happens only occasionally):
Tried this both in L2 and L3 mode of IPVLAN. Same results.

Output of docker version:

Server:
  Version: 17.06.2-ce
  API version: 1.30 (minimum version 1.12)
  Go version: go1.8.3
  Git commit: cec0b72
  Built: Tue Sep 5 19:59:11 2017
  OS/Arch: linux/amd64
  Experimental: true

Output of docker info:

Kernel: 4.4.0-96-generic
OS: Ubuntu 16.04.3 LTS

VMWare ESX

[thaJeztah]

ping @mavenugo @fcrisciani