"glibc not found" causes CrashLoopBackOff in fresh installation with helm

[yogeek]

I just followed the instructions to deploy sloop from helm chart : https://github.com/salesforce/sloop/blob/master/helm/sloop/README.md

I have not built the image but just deploy the chart with :

kubectl create ns sloop
helm template . --namespace sloop> sloop-test.yaml
kubectl -n sloop apply -f sloop-test.yaml

and the pod is in CrashLoopBackOff because of the following errors in the logs :

/sloop: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /sloop)
/sloop: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /sloop)

The image that has been deployed is ghcr.io/salesforce/sloop:latest

[isc-aray]

Having the same issue, but unfortunately, this project seems to be dead.

[isc-aray]

Just following back here. I was able to deploy a container with version tag sha-29123c2, but the more recent container builds are broken.

[sana-jawad]

@isc-aray Thanks for finding the issue. Can you please revert the changes or our team can also do it. Please let me know. Thanks!

[isc-aray]

@sana-jawad I'm not sure what's causing the issue, just that sha-29123c2 is the most recent container that deploys successfully.

[osassonSF]

@isc-aray @yogeek We have reverted the last commit which upgraded some dependencies and might be causing the issue. Can you please try to deploy and let us know if you are still facing the same issues?

[Bharath509]

@osassonSF even pulling the latest code I'm still facing the same issue.
@isc-aray I created a branch from the sha-29123c2, and followed the helm release process, But still getting the same issue.

[isc-aray]

@Bharath509 I just set image.tag to sha-29123c2 in my values.yaml.

[osassonSF]

@Bharath509 Can you try setting the image tag to sha-29123c2 and see if that works for you? If it doesn't, maybe you can try disabling the CGO_ENABLED flag through helm which could help (https://stackoverflow.com/questions/64421305/heroku-go-app-crashes-version-glibc-2-32-not-found-required-by-bin-main/76612769#76612769).

[123BLiN]

So this PR is not fixing anything imo and should be re-reverted
What helped in my case is to change builder to bullseye which probably has required libs while pure golang is not

FROM golang:1.19-bullseye as build

in the dockerfile