dockerfile: use lld linker for containerd build

[crazy-max]

closes #5546

[thaJeztah]

@crazy-max is this something that should also be applied to our containerd-packaging repo instead of the workaround we currently have (to install binutils-gold)?

[crazy-max]

@crazy-max is this something that should also be applied to our containerd-packaging repo instead of the workaround we currently have (to install binutils-gold)?

Either works but with cross comp, enforcing the linker is needed.

[tonistiigi]

This still needs some investigation. It's a combination of Go hardcoding linker to gold if arm64 and dynamic linux binary target https://github.com/golang/go/blob/go1.23.3/src/cmd/link/internal/ld/lib.go#L1661-L1673 . -buildmode=pie in https://github.com/containerd/containerd/blob/v2.0.0/Makefile.linux#L25 is one thing that triggers dynamic binary in here but not fully clear to me if only this or what the condition is. Hardcoding gold in go seems very bad to me as gold is not a (multi-)cross-compiling linker, and likely would not work on non-native GOOS. In this case this hardcoding completely messes up the config that is provided by xx leaving situation where cross-compiling C compiler works flawlessly, but if the same compiler is used for Cgo then it fails. If this won't be fixed (removed) in Go we likely need some override in xx to override the config again (eg. with hardcoding CGO_LDFLAGS). I still would like some clear examples of what condition triggers this and what is the containerd difference. Just removing the -buildmode=pie didn't seem to solve it on its own.