git-remote-https: Undefined symbol: EVP_md2, version OPENSSL_3.0.0

[piellick]

What happened?

Try to run a workspace with local docker(podman) on fedora 39.

{"type":"data","data":{"time":"2024-06-10T18:51:01.132092833+02:00","message":"Creating devcontainer...","level":"info"}}
{"type":"data","data":{"time":"2024-06-10T18:51:01.455082161+02:00","message":"Delete old workspace 'vscode-remote-try-php'","level":"info"}}
{"type":"data","data":{"time":"2024-06-10T18:51:01.78681207+02:00","message":"Cloning into '/home/pierrick/.devpod/agent/contexts/default/workspaces/vscode-remote-try-php/content'...","level":"info"}}
{"type":"data","data":{"time":"2024-06-10T18:51:01.806791707+02:00","message":"/usr/libexec/git-core/git-remote-https: symbol lookup error: /lib64/libldap.so.2: undefined symbol: EVP_md2, version OPENSSL_3.0.0","level":"info"}}
{"type":"error","error":{"time":"2024-06-10T18:51:01.811398588+02:00","message":"Cloning failed: clone repository: error cloning repository: exit status 128. Trying cloning on local machine and uploading folder","level":"error"}}
{"type":"data","data":{"time":"2024-06-10T18:51:01.811915353+02:00","message":"Cloning from host and upload folder to server","level":"info"}}
{"type":"data","data":{"time":"2024-06-10T18:51:01.84325187+02:00","message":"cloning local folder: EOF","level":"info"}}
{"type":"error","error":{"time":"2024-06-10T18:51:01.988294713+02:00","message":"Try enabling Debug mode under Settings to see a more verbose output","level":"error"}}
{"type":"error","error":{"time":"2024-06-10T18:51:01.988386277+02:00","message":"run agent command: Process exited with status 1","level":"fatal"}}

What did you expect to happen instead?

How can we reproduce the bug? (as minimally and precisely as possible)

Local Environment:

• DevPod Version: 0.5.12
• Operating System: linux AppImage
• ARCH of the OS: AMD64

DevPod Provider:

• Local/remote provider: docker

Anything else we need to know?

[piellick]

after upgrade to fedora 40:

{"type":"data","data":{"time":"2024-06-10T20:44:29.916965309+02:00","message":"Creating devcontainer...","level":"info"}}
{"type":"data","data":{"time":"2024-06-10T20:44:30.201526474+02:00","message":"Cloning into '/root/.devpod/agent/contexts/default/workspaces/vscode-remote-try-php/content'...","level":"info"}}
{"type":"data","data":{"time":"2024-06-10T20:44:30.222312412+02:00","message":"/usr/libexec/git-core/git-remote-https: /tmp/.mount_DevPod6RJo75/usr/lib/libssl.so.3: version `OPENSSL_3.2.0' not found (required by /lib64/libcurl.so.4)","level":"info"}}
{"type":"error","error":{"time":"2024-06-10T20:44:30.224881765+02:00","message":"Cloning failed: clone repository: error cloning repository: exit status 128. Trying cloning on local machine and uploading folder","level":"error"}}
{"type":"data","data":{"time":"2024-06-10T20:44:30.225431982+02:00","message":"Cloning from host and upload folder to server","level":"info"}}
{"type":"data","data":{"time":"2024-06-10T20:44:30.247932684+02:00","message":"cloning local folder: EOF","level":"info"}}
{"type":"error","error":{"time":"2024-06-10T20:44:30.888579891+02:00","message":"Try enabling Debug mode under Settings to see a more verbose output","level":"error"}}
{"type":"error","error":{"time":"2024-06-10T20:44:30.888775518+02:00","message":"run agent command: Process exited with status 1","level":"fatal"}}

[gbraad]

Same issue on Bazzite (Fedora 40) with the AppImage

[gbraad]

An alternative would be to force the use of ssh instead of the https-remote, eg:

[email protected]:/[orgname]/[reponame]

[Raltay]

I'm also experiencing the same issue on Bazzite with latest DevPod's AppImage.

I'd be grateful if somebody could suggest what the root cause might be and how to work around it (if possible).

Thank you in advance.

[bkneis]

thanks for reporting the issue @piellick, Does performing git clone on the repo you are using work?

[github-actions[bot]]

This issue is stale because it has been open for 60 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 30 days since being marked as stale.