oh! I recall I had a PR trying to do something similar, but I never got that to work; just in case it's useful, you could have a peek at it (if there's bit you could either use, or if there's other tests that should get the same treatment);

• Integration: cleanup custom "docker0" bridge after tests #39571
• I see it was linked to Testing: docker-py tests fail to build if run after integration(-cli) tests #39570

oh! I recall I had a PR trying to do something similar, but I never got that to work; just in case it's useful, you could have a peek at it (if there's bit you could either use, or if there's other tests that should get the same treatment);

Right, yes - same area ... I was mostly interested in tidying up the extra bridges, particularly for TestDaemonDefaultNetworkPools where they made a re-run of the test fail.

But, the changes also make sure docker0 is deleted if its address may have come from a modified address-pool.

I don't think modified default pool will necessarily be used in most of the tests, they don't delete docker0 first like TestDaemonDefaultNetworkPools does. They'll only use the defaults if they follow another test that deleted it, but the docker0 address seems irrelevant in most if not all of those tests. That could do with some more tidying, but this change at-least makes the tests re-runnable, and gets rid of some bridge devices they previously left behind.

I'll merge this ... there's undoubtedly more to do, but this is progress.

I'll merge this ... there's undoubtedly more to do, but this is progress.

Oh! Yes, for sure! Sorry, thought I replied 🙈