Investigate test with address already in use

[antho1404]

Sometime when running the tests we have the error

Address already in use, failed to allocate gateway (10.0.1.1): Address already in use

This shouldn't happen and need to be investigated and fixed to always have reliable builds

[ilgooz]

This can be related with a bug in docker or docker client:

• Lots of “failed to allocate gateway: Address already in use” in Docker CE 17.09.0 moby/moby#35204
• Creating docker swarm service leads to "failed to allocate gateway (10.0.4.1): Address already in use" moby/moby#35834

I investigated this issue for an hour yesterday but I didn't come up with a solid fix yet. Putting a 3 second sleep above the line of here or here solves this problem somehow. Maybe there is something async process going on when creating a network on docker's side or there is some name conflicts in network-service relationship.

But converting to unit tests should definitely solve this if we don't have a business logic mistake in our side.

[NicolasMahe]

This issue didn't occured for a long time. It should have been fixed with the fix on listening docker's event for network deletion.