MACVLAN support?

[thediveo]

Some of today's Docker scenarios require granting specific containers direct data-link layer ("MAC") access, as opposed to nat'ed IP access. Examples are not only (infamous?) license server containers, but also non-IP protocol-based applications, such as in some industrial environments. Docker comes with its CNM "macvlan" driver and the CNI "driver" base also supports MACVLAN.

At the moment (as of commit 2895d60) does not understand the -d option when creating a new network: for Docker, -d specifies the type of CNM driver to create a new network with. nerdctl compose also catches these case that try to specify a non-bridge network driver and blocks such projects from deployment.

Please support MACVLAN networks next to bridge networks in nerdctl for improved Docker-compatibility.

[AkihiroSuda]

Please support MACVLAN networks next to bridge networks in nerdctl for improved Docker-compatibility.

Feel free to open PR

[AkihiroSuda]

Implemented in #836

[thediveo]

Thank you very much! I'll see to put it through the paces of some unit tests on our side. Once again, thank you very much!