Containers unable to access network resources with Macvlan driver and vice versa

[mark1n]

If you are still interested in it, here may be the key for solving your problem:

Macvlan network and host to container connectity

Older versions of the docker documentation for mavlan networks included following note: When using macvlan, you cannot ping or communicate with the default namespace IP address. For example, if you create a container and try to ping the Docker host’s eth0, it will not work. That traffic is explicitly filtered by the kernel modules themselves to offer additional provider isolation and security. A macvlan subinterface can be added to the Docker host, to allow traffic between the Docker host and…

In my setup the docker host runs in a VM and I had to allow “promiscuous mode” on the vSwitch, otherwise the docker host net interface is not allowed to have more than one MAC address.