-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"glibc not found" causes CrashLoopBackOff in fresh installation with helm #270
Comments
Having the same issue, but unfortunately, this project seems to be dead. |
Just following back here. I was able to deploy a container with version tag sha-29123c2, but the more recent container builds are broken. |
@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! |
@sana-jawad I'm not sure what's causing the issue, just that sha-29123c2 is the most recent container that deploys successfully. |
@osassonSF even pulling the latest code I'm still facing the same issue. |
@Bharath509 I just set |
@Bharath509 Can you try setting the image tag to |
So this PR is not fixing anything imo and should be re-reverted
in the dockerfile |
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 :
and the pod is in
CrashLoopBackOff
because of the following errors in the logs :The image that has been deployed is
ghcr.io/salesforce/sloop:latest
The text was updated successfully, but these errors were encountered: