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
Hi Tomofumi,
it's me again. I've been using your library for quite a while now and occasionally I run into a race condition when two Vxlan links are created with the same name at the same time. Like this:
First vxlan link is created using MakeVxLan call for container c1, it's interface name is eth1
Before the first call gets to the SetVethLink, another vxlan links is created for container c2 but with the same name eth1.
Obviously the netlink.LinkAdd(&vxlanconf) fails for the second call with vxlan add failed: Failed to add vxlan eth1: file exists
I was wondering, would it be possible to do a similar trick that you do with veth pair, namely give it a temporary name and rename it only after it's been moved to the container's namespace?
The text was updated successfully, but these errors were encountered:
Hi Tomofumi,
it's me again. I've been using your library for quite a while now and occasionally I run into a race condition when two Vxlan links are created with the same name at the same time. Like this:
MakeVxLan
call for container c1, it's interface name iseth1
SetVethLink
, another vxlan links is created for container c2 but with the same nameeth1
.netlink.LinkAdd(&vxlanconf)
fails for the second call withvxlan add failed: Failed to add vxlan eth1: file exists
I was wondering, would it be possible to do a similar trick that you do with veth pair, namely give it a temporary name and rename it only after it's been moved to the container's namespace?
The text was updated successfully, but these errors were encountered: