2.276.1 @ Ubuntu 18.04: `ldd: ./bin/libSystem.Security.Cryptography.Native.OpenSsl.so: No such file or directory`
See original GitHub issueDescribe the bug I’m trying to install a self-hosted runner on Ubuntu 18.04 using the automation script and I get the following errors:
~$ curl -s https://raw.githubusercontent.com/actions/runner/automate/scripts/create-latest-svc.sh | bash -s ***/*** ***-runner
Configuring runner @ ***/***
/usr/bin/curl
/usr/bin/jq
Generating a registration token...
Downloading latest runner ...
Downloading v2.276.1 for linux ...
https://github.com/actions/runner/releases/download/v2.276.1/actions-runner-linux-x64-2.276.1.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 665 100 665 0 0 24629 0 --:--:-- --:--:-- --:--:-- 24629
100 70.5M 100 70.5M 0 0 90.1M 0 --:--:-- --:--:-- --:--:-- 95.5M
-rw-rw-r-- 1 *** *** 73928496 Jan 27 10:47 actions-runner-linux-x64-2.276.1.tar.gz
Extracting actions-runner-linux-x64-2.276.1.tar.gz to ./runner
~/runner ~
Configuring jenkins-runner @ https://github.com/***/***
./config.sh --unattended --url https://github.com/***/*** --token *** --name ***-runner
ldd: ./bin/libSystem.Security.Cryptography.Native.OpenSsl.so: No such file or directory
ldd: ./bin/libSystem.IO.Compression.Native.so: No such file or directory
---
# Authentication
√ Connected to GitHub
# Runner Registration
√ Runner successfully added
√ Runner connection is good
# Runner settings
√ Settings Saved.
The runner reports to be started successfully but the errors seem to be related to .NET upgrade from v3 to v5 and I’m unsure if I can rely on the runner working correctly.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:15 (2 by maintainers)
Top Results From Across the Web
How do I install the OpenSSL libraries on Ubuntu?
Try typing sudo apt-get install libssl and then hit tab to see a list of matching package names (which can help when you...
Read more >How do I use OpenSSL 1.1.1 in Ubuntu 22.04?
In my case, I faced similar issue because of openssl 3.x move from 1.1.x., such as errors as: VERIFY ERROR: depth=0, error=CA signature ......
Read more >runtime.ubuntu.18.04-x64.runtime.native.System.Security. ...
Internal implementation package not meant for direct consumption. Please do not reference directly. When using NuGet 3.x this package ...
Read more >USN-6039-1: OpenSSL vulnerabilities
Details. It was discovered that OpenSSL was not properly managing file locks when processing policy constraints. If a user or automated system ...
Read more >libssl.so.6 cannot open shared object file' even after I run ...
From the ldd command it looks like the binary is looking in /lib/x86_64-linux-gnu and not /usr/lib/x86_64-linux-gnu where you found the ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Still seeing this with the latest version
Still experiencing this when running
./config.sh
ldd: ./bin/libcoreclr.so: No such file or directory ldd: ./bin/System.Security.Cryptography.Native.OpenSsl.so: No such file or directory ldd: ./bin/System.IO.Compression.Native.so: No such file or directory ./config.sh: line 80: ./bin/Runner.Listener: cannot execute binary file: Exec format error