This is generally only true with CGO_ENABLED=0. I've found many times that a go binary, even if it has no cgo or cgo dependencies, will randomly require glibc

This is generally only true with CGO_ENABLED=0. I've found many times that a go binary, even if it has no cgo or cgo dependencies, will randomly require glibc on the target system to execute if you don't explicitly disable cgo in your build.