"glibc not found" causes CrashLoopBackOff in fresh installation with helm about sloop HOT 9 OPEN

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

from sloop.

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

from sloop.

@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?

from sloop.

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

from sloop.

@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!

from sloop.

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

from sloop.

@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.

from sloop.

@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).

from sloop.

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

from sloop.