search

jpetazzo / pipework

Software-Defined Networking tools for LXC (LinuX Containers)
Apache License 2.0
4.22k stars 727 forks source link

randomize interface names to avoid conflicts #148

Closed AkihiroSuda closed 9 years ago

AkihiroSuda commented 9 years ago

I create and remove containers frequently, and sometimes got an error like this:

ovs-vsctl: cannot create a port named veth1pl16704 because a port named veth1pl16704 already exists on bridge ovsbr0

This patch fixes this.

jpetazzo commented 9 years ago

Since the interface name is already set to use the container PID (which should be unique!) the issue should arise only if you are trying to run pipework twice, simultaneously, on the same container. Is that the case?

AkihiroSuda commented 9 years ago

The issue had arisen even when I run single pipework instance.

However, 7e9987 seems to have already resolved the issue. So I would like to close this ticket.

jpetazzo commented 9 years ago

OK, thanks!