On Sun, 5 Jan 2025 15:07:30 +0000 Rob Murray <[email protected]> wrote: > Package: docker.io > Version: 26.1.5+dfsg1 / 26.1.5+dfsg1-4+b1 > > Hi all, this is related to https://github.com/moby/moby/issues/49197 - > "Cannot connect container to custom bridge network: cannot program > address in sandbox interface because it conflicts with existing > route". > > The upstream moby 26.1.5 uses Go package > "github.com/vishvananda/netlink v1.2.1-beta.2". The Trixie-packaged > version seems to be using an updated version, "1.3.0" perhaps. But, > the "vishvananda/netlink" project didn't follow the "semver" rules in > this case - its 1.2.1 release included breaking changes. > > The cause of the specific issue reported in the moby ticket above is > described at https://github.com/moby/moby/pull/48368#issuecomment-2307593543 > - and was addressed in that PR (to ship in moby 28.0). > > Another issue with changes in the netlink package was addressed by > https://github.com/moby/moby/pull/48407.
Oof, this is clearly not ideal (de-vendoring is never dull, that's for sure)! To be clear, do we need to backport the non-vendor bits of https://github.com/moby/moby/pull/48368 to the 26.1.5 currently in unstable/testing to fix this? Do we actually need the slightly larger set of changes that ended up in https://github.com/moby/moby/pull/48938? Something else? (The latter is what I tried first, and it doesn't apply cleanly to 26.1.5 as-is, so I guess more digging/work is required. 🙈) ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4
