Docker Container on Alternative VLAN & Subnet

[meyay (Metin Y.)]

We still prefer valid yaml content, as It’s cumbersome to read it, if it’s not properly formatted and can hide other problems with the compose file content.

The forum search should have found a couple of useful topics about macvlan.

@https://forums.docker.com/t/segregating-docker-networks/142931/2

Note: a macvlan child interface (those that containers use) can not communicate with their parent interface and vice versa. This behavior is caused by a kernel security feature, and not by Docker itself. Adding a macvlan child interface (often refers to as shim) to the host, allows communication between this interface and other macvlan child interfaces. A container can still not communicate with the parent interface’s ip, but it can communicate with the added host child interface.

Most likely this is what causes the problem.

This solution should appy to your case as well.