runner: 2.276.1 @ Ubuntu 18.04: `ldd: ./bin/libSystem.Security.Cryptography.Native.OpenSsl.so: No such file or directory`

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

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 2
  • Comments: 16 (2 by maintainers)

Most upvoted 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

sed -i -e 's/libSystem./System./g' config.sh will do the trick as well, as ldd wants to check wrong filenames within config.sh

I was struggling with this and realized it was PEBKAC. I was trying to install the MacOS runner on Linux. Check and make sure you aren’t doing the same.

I saw the exact same message as @NoelOmo and @eumoh1601. The problem was I had downloaded the runner for macOS, and then tried to install it on Linux.

Symlinking the expected library paths to the actual library paths seems to resolve the errors:

cd runner/bin
for lib in $(find . -name 'System.*'); do
    toFile=$(echo "$lib" | sed -e 's/\.\/System\./.\/libSystem./g')
    if ! [ -f $toFile ]; then 
        sudo ln -s $lib $toFile
    fi
done

Credits go to this stackoverflow user.

@hross Hit this with 2.286.0, though only when using an arm64 executor