Thanks for the details. So I just uploaded a new version in experimental, it is 20.10.0~rc1+dfsg3-1. In this version docker.io vendors the old go-radix, as suggested.
If someone can give it a try and confirm that indeed the bug is fixed, that would be great. Thanks again. Arnaud On Wed, Dec 2, 2020 at 12:48 AM Shengjing Zhu <z...@debian.org> wrote: > Sadly I see it in my log too. So after searching a bit, I find this > > https://github.com/moby/libnetwork/pull/2581 > > So it's indeed caused by golang-github-armon-go-radix-dev 1.0.0 > > And docker maintainer has proposed a patch to go-radix, > https://github.com/armon/go-radix/pull/14 > But reading from the issue, it seems docker just implemented in the wrong > way. > > So I suggest vendoring the old go-radix... > > On Mon, Sep 16, 2019 at 1:53 PM Arnaud Rebillout > <arnaud.rebill...@collabora.com> wrote: > > > > > > From: Vincent Smeets <vincent.vsme...@gmail.com> > > > > Using journalctl, I see the following error: > > > > panic: runtime error: invalid memory address or nil pointer dereference > > [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 > pc=0x564a9d3a2158] > > goroutine 439 [running]: > > github.com/armon/go-radix.recursiveWalk(0x0, 0xc4212bddb8, 0xc4212bdc00) > > /build/docker.io-18.06.1+dfsg1/.gopath/src/ > github.com/armon/go-radix/radix.go:477 +0x28 > > > > > > Hans, do you also see the same logs in the journal? (trying to be sure > it's the same issue) > > > > docker-ce builds against armon/go-radix > e39d623f12e8e41c7b5529e9a9dd67a1e2261f80, Jan 2015 [1] > > > > docker.io builds against armon/go-radix v1.0, Aug 2018 [2], as you can > see with: > > > > $ rmadison golang-github-armon-go-radix-dev > > golang-github-armon-go-radix-dev | 1.0.0-1 | > stable | all > > golang-github-armon-go-radix-dev | 1.0.0-1 | > unstable | all > > > > That could be the issue. Now, I don't know if you hit a bug in go-radix > v1.0, or if you hit an incompatibility between docker and the version v1.0 > of go-radix. > > > -- > Shengjing Zhu >
