Closed rico-chet closed 1 year ago
I found two issues related to this: https://github.com/golang/go/issues/58550 https://github.com/golang/go/issues/57328
I see two possible reasons for this issue. We build mob with an ubuntu-latest on github actions which have a newer version of glibc. Second reason we are now using go 1.20 which just dynamically link the glibc dependency at runtime and does not ship its own compiled version.
We need to think about who we will proceed here.
Thank you @rico-chet
@hollesse you mean using CGO_ENABLED=0
?
@gregorriegler Could be one option. But I am not sure if we need glibc. There we need to further investigate. One point for glibc could be our network request we are doing for the timer. Maybe there is also an option to just statically link it again as it was in the go release we used before.
one more resource i found, which should help us. https://mt165.co.uk/blog/static-link-go/
should be fixed with 3e849a243a8ed3a8ef4aa3d81ac8dee6ab35903d tested it on ubuntu 21. So the next release should work again :)
confirm that 4.4.5 works in a Debian 10.0 container
Doesn't run on a 2019 OS.
Will probably not run on Debian 11, either (released 2021, has glibc 2.31)
Debian 10 is what we use in our dev container because Debian 11 has a broken
make
.