You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to create macvlan private network for swarm service to communicate with non-docker system on the same VLAN.
In my case I have to create template networks for the macvlan one.
If I create the network as internal then containers can't communicate with each other.
If I create the network as non-internal it will change default gateway and break communication with rest of my network.
It's not possible to create internal config-only network.
Internal parameter of the config-from network is overwritten by the config-only network.
Dummy interface is used as parent interface of the config-from private_net.
Describe the results you expected:
The private_net should use interface specified in it's config-from network.
Existing default gateway in container should not be changed for internal macvlan network.
Additional information you deem important (e.g. issue happens only occasionally):
I can create network without the --internal parameter but in such case it will change default gateway to non-existent ip from the network ip range which breaks communication.
Output of docker version:
Client:
Version: 18.09.6
API version: 1.39
Go version: go1.10.8
Git commit: 481bc77
Built: Sat May 4 02:36:00 2019
OS/Arch: linux/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 18.09.6
API version: 1.39 (minimum version 1.12)
Go version: go1.10.8
Git commit: 481bc77
Built: Sat May 4 01:59:36 2019
OS/Arch: linux/amd64
Experimental: false
lemrouch
changed the title
Containers can't communicate over macvlan network in swarm
Containers can't communicate over macvlan internal network in swarm
Jun 24, 2019
Description
I'm trying to create macvlan private network for swarm service to communicate with non-docker system on the same VLAN.
In my case I have to create template networks for the macvlan one.
If I create the network as internal then containers can't communicate with each other.
If I create the network as non-internal it will change default gateway and break communication with rest of my network.
It's not possible to create internal config-only network.
Steps to reproduce the issue:
create config-only networks:
on node1:
docker network create --config-only --subnet 10.20.30.0/24 -o parent=enp1s0.30 --ip-range 10.20.30.192/27 private_net_template
on node2:
docker network create --config-only --subnet 10.20.30.0/24 -o parent=enp1s0.30 --ip-range 10.20.30.224/27 private_net_template
create network:
docker network create -d macvlan --internal --scope swarm --attachable --config-from private_net_template private_net
Describe the results you received:
Internal parameter of the config-from network is overwritten by the config-only network.
Dummy interface is used as parent interface of the config-from private_net.
Describe the results you expected:
The private_net should use interface specified in it's config-from network.
Existing default gateway in container should not be changed for internal macvlan network.
Additional information you deem important (e.g. issue happens only occasionally):
I can create network without the --internal parameter but in such case it will change default gateway to non-existent ip from the network ip range which breaks communication.
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
This was tested on linux KVM VMs but this doesn't really matter.
The text was updated successfully, but these errors were encountered: