/lib64/libc.so.6: version `GLIBC_2.32' not found when building on linux

[pohzipohzi]

I was running into this error when I followed the instructions in the README:

/var/task/main: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /var/task/main)

I managed to fix it via by setting CGO_ENABLED=0 when building on linux, similar to the instructions for windows, ie

GOOS=linux GOARCH=amd64 CGO_ENABLED=0 go build -o main main.go

Should that be included in the README, or is there a better way to fix this?

[bmoffatt]

yeah, I can add a note about CGO in the README. Amazon Linux 1/2 provides glibc 2.17/2.26, so I can see how this'd be a problem depending on a developer's Linux distro.

[mrwormhole]

I have witnessed this one today, seems like it is just a problem of using CGO when the C library you have under the hood is not compatible with glibc 2.32 or there is no C library but you are trying to build with CGO, therefore, it can not detect/find the correct version for .so files. It took the production down for 1 hour, just because of CGO_ENABLED=1

CGO should never be used and it should be avoided as much as possible just like the reflection

https://dave.cheney.net/2016/01/18/cgo-is-not-go

[LeonardoFurtado]

It works. @bmoffatt Is this issue still required to be open?

[HSchmale16]

Affected by the same issue. Trying to use SQLite with go on lambda is painful.

[ccampo133]

Just ran into this myself also trying to use go-sqlite3. @HSchmale16 did you ever find a way to get it to work?

[HSchmale16]

Just ran into this myself also trying to use go-sqlite3. @HSchmale16 did you ever find a way to get it to work?

I ended up building and deploying from cloudshell. Had to move the GOPATH to outside of the home directory. I still haven't fully understood what lambda is doing with it.

[ccampo133]

Gotcha - in that case the solution is probably to build the binary on some form of Amazon Linux (VM, container, etc).

[ccampo133]

Just to follow up - confirmed at least in my case if I build the Go binary (which requires cgo, particularly using go-sqlite3) on Amazon Linux, it will execute successfully. Specifically, I used the amazonlinux:2 Docker image, installed Go on it, and built the binary in that.

[HSchmale16]

@ccampo133 I've documented my fix on my blog. See link for details.

https://www.henryschmale.org/2022/09/29/go-in-cloudshell.html

[gauntface]

I ran into this while using the SAM CLI.

The fix was ultimately the suggestion to use CGO_ENABLED=0 but I had to take some additional steps to make this work with sam, see aws/aws-sam-cli#3894 for the breadcrumbs.

Documented the approach for my project here: https://www.gaunt.dev/blog/2022/glibc-error-with-aws-sam-and-go/

[ccampo133]

@gauntface that will only work if your project does not depend on cgo. In my (and others here) case, I required cgo for go-sqlite3, which requires special compilation specifically for the Lambda Go runtime environment.