-
Notifications
You must be signed in to change notification settings - Fork 108
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
ls-remote fails inside docker container with "undefined symbol: curl_global_sslset" #351
Comments
Seems to have started happening since we upgraded from 1.93 if that helps. Let me know if there's anything else we can do to help diagnose it. |
Ouch! Sorry about that @mattwynne! I think 1.94 was the first version of dugite-native we built with GitHub Actions instead of whatever was used before, and we already found some issues related to libcurl on macOS (see desktop/desktop#11516). I think the problem is related to whatever libcurl is installed in the GitHub Action runner. We'd need to take a look. Also I think this issue should be in the https://github.com/desktop/dugite-native repo (affecting https://github.com/desktop/dugite-native/tree/v2.26.2-4 and newer), so I'll move it there 😄 Thanks for reporting this! ❤️ |
No worries @sergiou87 it's a great solid library most of the time and we get a lot of value from it, thanks to you and the other maintainers. |
I encounter this error trying to run against CentOS-7(which we are maintaining support for until June 30, 2024). To fix it, I ended up building git against a lower version of libcurl(specifically the one that ships with CentOS-7): gitkraken#2 I made modifications for all linux arch's but I didn't confirm it works on any of them except x64-linux because that's the only one we support currently. |
I've got some code that runs fine on my local (OS X) dev machine, but when I run it inside a docker container (based off of the
node:14.14.0
image), it fails with this error:This is coming from a line that's trying to run
ls-remote
on anhttps://
remote URL.Any ideas why this is happening and what we can do?
The text was updated successfully, but these errors were encountered: