hugo v0.125.0: `GLIBC_2.29' not found

[AbeEstrada]

Environment:

• hugo_extended_0.125.0_linux-arm64.tar.gz
• aws/codebuild/amazonlinux-aarch64-lambda-standard:go1.21

I'm downloading v0.125.0 and when I try to run it in AWS Codebuild and I get this error:

[Container] 2024/04/16 10:44:07.651396 Running command ./hugo version
./hugo: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by ./hugo)
./hugo: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by ./hugo)

[Container] 2024/04/16 10:44:07.661479 Command failed with exit status 1

This is not happening with v0.124.0

[fu-sen]

I'm running into this problem with a Vercel build:

[10:59:43.490] Running build in Washington, D.C., USA (East) – iad1
[10:59:43.672] Retrieving list of deployment files...
[10:59:44.324] Downloading 316 deployment files...
[10:59:46.130] Restored build cache
[10:59:46.215] Running "vercel build"
[10:59:46.786] Vercel CLI 33.7.1
[10:59:46.898] fatal: not a git repository (or any of the parent directories): .git
[10:59:47.405] Installing Hugo version 0.125.0
[10:59:48.083] Installing dependencies...
[10:59:48.820] 
[10:59:48.820] up to date in 306ms
[10:59:48.831] hugo: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by hugo)
[10:59:48.831] hugo: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by hugo)
[10:59:48.833] Error: Command "hugo --minify --gc" exited with 1
[10:59:49.024] 

This also occurred after updating to v0.125.0. I was able to build successfully up to v0.124.1.

[agriyakhetarpal]

Does this work if you switch to a newer Docker image, i.e., aws/codebuild/amazonlinux-aarch64-lambda-standard:go1.22? This is because Hugo v0.125.0 bumps the version of Go being used for the compilation to v1.22.2.

[bep]

I have checked and I made a mistake when I upgraded the build image for Go 1.22. I apologise. I will push a fix later today.

[fu-sen]

I updated hugo to v0.125.1. This problem is resolved and it is working fine. (Vercel build) thank you!

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.