Add support for Alpine and other musl-based Linux distributions #331

SeanMsi · 2021-12-07T21:18:21Z

Hi,

We've recently discovered an issue while using ClearScript version 7.2.0.

When trying to use ClearScript in an Alpine Docker Image, the following error occurs:

Unhandled exception. System.TypeLoadException: Cannot load ClearScript V8 library. Load failure information for ClearScriptV8.linux-x64.so:
/app/runtimes/linux-x64/native/ClearScriptV8.linux-x64.so: Unable to load shared library '/app/runtimes/linux-x64/native/ClearScriptV8.linux-x64.so' or one of its dependencies. In order to help diagnose loading problems, consider setting the LD_DEBUG environment variable: Error loading shared library ld-linux-x86-64.so.2: No such file or directory (needed by /app/runtimes/linux-x64/native/ClearScriptV8.linux-x64.so)

Adding the glibc compatability layer to try and solve this causes the following error:

terminate called after throwing an instance of 'std::system_error'
 what():  No error information

Going back to version 7.0.0 with the glibc compatability layer works in an Alpine image without issues. Maybe this was caused by the following change in 7.1?:

Switched to static linking of C/C++ libraries to broaden Linux support

Steps to reproduce

Create simple C# project using ClearScript 7.2.0

static void Main(string[] args)
{
	var engine = new V8ScriptEngine();
	engine.AddHostType("Console", typeof(Console));
	engine.Evaluate("Console.WriteLine('Hello from JS')");
}

Build/Publish project (dotnet build && dotnet publish)

Build Docker image with:

Alpine base (such as mcr.microsoft.com/dotnet/aspnet:5.0-alpine)
Alpine's glibc compatability layer (RUN apk add gcompat)
Copy dotnet publish output and set the entrypoint to simple app

Run the Docker image and output should be the error shown above

The text was updated successfully, but these errors were encountered:

ClearScriptLib · 2021-12-08T18:43:53Z

Hi @SeanMsi,

We've reproduced the issue with ClearScript 7.2 on Alpine in WSL. For us, ClearScript 7.0 with gcompat doesn't work either, failing quietly as soon as we try to instantiate V8ScriptEngine. There's no error message, no core dump, nothing.

Anyway, it looks like Alpine requires special .NET SDK and runtime builds for some reason, and ClearScript could be in the same boat. Unfortunately, as it's a side project, supporting the three major desktop platforms – including the eight platform-specific V8 packages – is already stretching the limits of the resources available.

Sorry!

William-Froelich · 2021-12-18T02:58:56Z

I built the latest mainline in an linux container and debugged in alpine. I was able to reproduce the error:

terminate called after throwing an instance of 'std::system_error'
  what():  No error information

There's an exception coming from a missing dependency linkage.

Exception has occurred: CLR/System.DllNotFoundException
Exception thrown: 'System.DllNotFoundException' in System.Private.CoreLib.dll: 'Unable to load shared library '/workspaces/ClearScript/MuslTest/bin/Debug/net6.0/runtimes/linux-x64/native/ClearScriptV8.linux-x64.so' or one of its dependencies. In order to help diagnose loading problems, consider setting the LD_DEBUG environment variable: Error loading shared library /workspaces/ClearScript/MuslTest/bin/Debug/net6.0/runtimes/linux-x64/native/ClearScriptV8.linux-x64.so: No such file or directory'
   at System.Runtime.InteropServices.NativeLibrary.LoadFromPath(String libraryName, Boolean throwOnError)
   at System.Runtime.InteropServices.NativeLibrary.Load(String libraryPath)
   at Microsoft.ClearScript.V8.V8Proxy.LoadLibrary(String path) in /workspaces/ClearScript/ClearScript/V8/V8Proxy.NetCore.c

I'm going to keep looking, but does this give any more insight?

William-Froelich · 2021-12-18T05:15:10Z

The exception in my previous message was my fault. I wasn't copying the lib to the expected subpath.

Update:
After fixing the above issue, I debugged it through to gthr-default.h. __gthread_active_p() returns false when checking to see if __thread_active_ptr has been set. After this, flow control proceeds to the end of std::call_once(). SIGABRT is thrown shortly after.

That make it seem to be related to threading not running | being supported | not detected at runtime. I'm not sure what the fix is exactly, but I did see on a quick glance through github issues elsewhere that there's been some issue with threading when compiled on gcc and run on musl. I don't know if these issues are related or not.

Exception displayed by GDB

Exception has occurred.
Unknown stopping event

Stack Trace from V8Environment_InitializeICU

ClearScriptV8.linux-x64.so!__gthread_active_p()() (\usr\include\c++\10.3.1\x86_64-alpine-linux-musl\bits\gthr-default.h:252)
ClearScriptV8.linux-x64.so!__gthread_once(int*, void (*)())() (\usr\include\c++\10.3.1\x86_64-alpine-linux-musl\bits\gthr-default.h:699)
ClearScriptV8.linux-x64.so!void std::call_once<void (&)()>(std::once_flag&, void (&)())() (\usr\include\c++\10.3.1\mutex:729)
ClearScriptV8.linux-x64.so!icu_69::UMutex::getMutex()() (\workspaces\ClearScript\V8\build\v8\third_party\icu\source\common\umutex.cpp:83)
ClearScriptV8.linux-x64.so!icu_69::UMutex::lock()() (\workspaces\ClearScript\V8\build\v8\third_party\icu\source\common\umutex.h:235)
ClearScriptV8.linux-x64.so!umtx_lock_69() (\workspaces\ClearScript\V8\build\v8\third_party\icu\source\common\umutex.cpp:116)
ClearScriptV8.linux-x64.so!setCommonICUData(UDataMemory*, signed char, UErrorCode*)() (\workspaces\ClearScript\V8\build\v8\third_party\icu\source\common\udata.cpp:187)
ClearScriptV8.linux-x64.so!udata_setCommonData_69() (\workspaces\ClearScript\V8\build\v8\third_party\icu\source\common\udata.cpp:909)
ClearScriptV8.linux-x64.so!v8::internal::InitializeICU(char const*)() (\workspaces\ClearScript\V8\build\v8\src\init\icu_util.cc:93)
ClearScriptV8.linux-x64.so!V8Environment_InitializeICU(const StdChar * pDataPath) (\workspaces\ClearScript\ClearScriptV8\V8SplitProxyNative.cpp:122)
[Unknown/Just-In-Time compiled code] (Unknown Source:0)

SIGABRT Stack Trace

ld-musl-x86_64.so.1!setjmp (Unknown Source:0)
ld-musl-x86_64.so.1!raise (Unknown Source:0)
ld-musl-x86_64.so.1![Unknown/Just-In-Time compiled code] (Unknown Source:0)

Debug Console:

Thread 1 "dotnet" received signal SIGABRT, Aborted.
0x00007ff9da4353f2 in setjmp () from /lib/ld-musl-x86_64.so.1

ClearScriptLib · 2021-12-20T04:48:43Z

Hi @William-Froelich,

Thanks for looking into this.

That make it seem to be related to threading not running | being supported | not detected at runtime.

Hmm, std::call_once is a standard C++ API, so std::system_error probably indicates a serious library mismatch of some sort. Note that ClearScript explicitly specifies pthread linkage here.

I did see on a quick glance through github issues elsewhere that there's been some issue with threading when compiled on gcc and run on musl.

ClearScript uses Clang to build its native Linux libraries. A quick search suggests that Clang may support a special target for musl.

Please keep us posted on any additional insights or discoveries.

Thank you!

William-Froelich · 2022-01-06T00:00:47Z

I've tried recompiling against musl but I've hit a few issues I'm hoping someone can advise on.

The libv8 download step fails and I'm looking into what might be the cause. Is this something anyone else has seen before? The docker container I'm running in has Python 2.7 so I don't think it's specifically related to the python version.

I'm going to keep looking into the V8 project to see if I can figure something out.

vscode ➜ /workspaces/ClearScript (musl-debug-experiment ✗) $ make -f ./Unix/Makefile DEBUG=1
make -f /workspaces/ClearScript/Unix/ClearScriptV8/Makefile
make[1]: Entering directory '/workspaces/ClearScript'
cd /workspaces/ClearScript/Unix; ./V8Update.sh -n -y x64 Debug
Build: x64 Debug
*** BUILD DIRECTORY NOT FOUND; DOWNLOAD REQUIRED ***
V8 revision: Tested (9.6.180.14)
Creating build directory ...
Downloading Depot Tools ...
Downloading V8 and dependencies ...
WARNING: Your metrics.cfg file was invalid or nonexistent. A new one will be created.
Error: Command 'vpython third_party/depot_tools/update_depot_tools_toggle.py --disable' returned non-zero exit status 1 in /workspaces/ClearScript/V8/build/v8
[E2022-01-05T23:06:54.723430Z 5211 0 annotate.go:273] goroutine 1:
#0 go.chromium.org/luci/vpython/venv/config.go:309 - venv.(*Config).resolvePythonInterpreter()
  reason: none of [/workspaces/ClearScript/V8/build/depot_tools/[email protected]_bin/python/bin/python] matched specification 2.7.0

#1 go.chromium.org/luci/vpython/venv/config.go:153 - venv.(*Config).resolveRuntime()
  reason: failed to resolve system Python interpreter

#2 go.chromium.org/luci/vpython/venv/venv.go:143 - venv.With()
  reason: failed to resolve python runtime

#3 go.chromium.org/luci/vpython/run.go:60 - vpython.Run()
#4 go.chromium.org/luci/vpython/application/application.go:327 - application.(*application).mainImpl()
#5 go.chromium.org/luci/vpython/application/application.go:416 - application.(*Config).Main.func1()
#6 go.chromium.org/luci/vpython/application/support.go:46 - application.run()
#7 go.chromium.org/luci/vpython/application/application.go:415 - application.(*Config).Main()
#8 vpython/main.go:112 - main.mainImpl()
#9 vpython/main.go:118 - main.main()
#10 runtime/proc.go:225 - runtime.main()
#11 runtime/asm_amd64.s:1371 - runtime.goexit()

*** THE PREVIOUS STEP FAILED ***
make[1]: *** [/workspaces/ClearScript/Unix/ClearScriptV8/Makefile:140: /workspaces/ClearScript/V8/build/v8/out/x64/Debug/obj/libv8_monolith.a] Error 1
make[1]: Leaving directory '/workspaces/ClearScript'
make: *** [Unix/Makefile:24: all] Error 2

V8SplitProxyNative.tt seems to assume just arch and os are needed to determine the native library to load. This probably would need to get changed, though I'm not clear what could be done to determine if musl is in use instead of glibc. This class is used to generate V8SplitProxyNativeGenerated.cs right?
Packaging - I assume this would have to be a brand new nuget package and not just added to Microsoft.ClearScript.V8.Native.Linux-* packages?

ClearScriptLib · 2022-01-06T17:54:55Z

Hi @William-Froelich,

Thanks for investigating this!

none of [/workspaces/ClearScript/V8/build/depot_tools/[email protected]_bin/python/bin/python] matched specification 2.7.0

Not sure what's going on there. On Ubuntu LTS, that path is Python 2.7.18. What happens when you run it in your container?

This class is used to generate V8SplitProxyNativeGenerated.cs right?

Yes. It'd probably be best to treat this as a new architecture – perhaps something like "x64_musl". For the native call routing to work as it does today, we'd need to be able to detect this architecture at runtime. Currently we use RuntimePlatform.OSArchitecture, but we'd need some other technique to differentiate between musl and glibc.

I assume this would have to be a brand new nuget package and not just added to Microsoft.ClearScript.V8.Native.Linux-* packages?

We might be able to make it work either way, but a separate package would probably be best.

Thanks again, and please keep us posted!

William-Froelich · 2022-01-06T19:32:18Z

Not sure what's going on there. On Ubuntu LTS, that path is Python 2.7.18. What happens when you run it in your container?

In the alpine container the path is what I would expect and the version matches Ubuntu:

vscode ➜ /workspaces/ClearScript/V8/build (musl-debug-experiment ✗) $ which python
/usr/bin/python
vscode ➜ /workspaces/ClearScript/V8/build (musl-debug-experiment ✗) $ ls -al /usr/bin/python
lrwxrwxrwx 1 root root 7 Jan  5 22:43 /usr/bin/python -> python2
pythjovscode ➜ /workspaces/ClearScript/V8/build (musl-debug-experiment ✗) $ 
vscode ➜ /workspaces/ClearScript/V8/build (musl-debug-experiment ✗) $ python --version
Python 2.7.18

Running python from the depot_tools directory seems to indicate the minimal libc on alpine isn't sufficient due to the symbol not found errors.

vscode ➜ /workspaces/ClearScript/V8/build (musl-debug-experiment ✗) $ /workspaces/ClearScript/V8/build/depot_tools/[email protected]_bin/python/bin/python
Error relocating /workspaces/ClearScript/V8/build/depot_tools/[email protected]_bin/python/bin/python2.7: xdr_pointer: symbol not found
Error relocating /workspaces/ClearScript/V8/build/depot_tools/[email protected]_bin/python/bin/python2.7: clnt_perror: symbol not found
Error relocating /workspaces/ClearScript/V8/build/depot_tools/[email protected]_bin/python/bin/python2.7: clnt_pcreateerror: symbol not found
Error relocating /workspaces/ClearScript/V8/build/depot_tools/[email protected]_bin/python/bin/python2.7: xdr_bool: symbol not found
Error relocating /workspaces/ClearScript/V8/build/depot_tools/[email protected]_bin/python/bin/python2.7: xdr_opaque: symbol not found
Error relocating /workspaces/ClearScript/V8/build/depot_tools/[email protected]_bin/python/bin/python2.7: xdr_u_int: symbol not found
Error relocating /workspaces/ClearScript/V8/build/depot_tools/[email protected]_bin/python/bin/python2.7: xdr_bytes: symbol not found
Error relocating /workspaces/ClearScript/V8/build/depot_tools/[email protected]_bin/python/bin/python2.7: clnt_spcreateerror: symbol not found
Error relocating /workspaces/ClearScript/V8/build/depot_tools/[email protected]_bin/python/bin/python2.7: xdr_char: symbol not found
Error relocating /workspaces/ClearScript/V8/build/depot_tools/[email protected]_bin/python/bin/python2.7: xdr_enum: symbol not found
Error relocating /workspaces/ClearScript/V8/build/depot_tools/[email protected]_bin/python/bin/python2.7: xdr_vector: symbol not found
Error relocating /workspaces/ClearScript/V8/build/depot_tools/[email protected]_bin/python/bin/python2.7: xdr_free: symbol not found
Error relocating /workspaces/ClearScript/V8/build/depot_tools/[email protected]_bin/python/bin/python2.7: xdr_string: symbol not found
Error relocating /workspaces/ClearScript/V8/build/depot_tools/[email protected]_bin/python/bin/python2.7: clnt_create: symbol not found

I guess I can try to build with musl on ubuntu and copy to alpine and see if that works.

ClearScriptLib · 2022-01-07T14:01:30Z

Yeah, the V8 build process is finicky about its platform. For example, all 32-bit versions must be cross-compiled. Apparently, it's now using its own glibc-based Python.

William-Froelich · 2022-01-07T23:31:57Z

I was trying out the musl compilation without adding the higher-level changes (just replacing the existing linux-64.so with the musl version). I built on ubuntu and then swapped to alpine linux to test.

You can view the diff here: William-Froelich#1

I verified the library builds targeting musl instead of glibc with ldd:

vscode ➜ /workspaces/ClearScript/MuslTest (musl-debug-experiment ✗) $ ldd ./bin/Debug/net6.0/ClearScriptV8.linux-x64.so 
        /lib/ld-musl-x86_64.so.1 (0x7f5ab030b000)
        libm.so.6 => /lib/ld-musl-x86_64.so.1 (0x7f5ab030b000)
        libpthread.so.0 => /lib/ld-musl-x86_64.so.1 (0x7f5ab030b000)
        libc.so => /lib/ld-musl-x86_64.so.1 (0x7f5ab030b000)

Unfortunately, the error output is exactly the same and the app crashes right after executing std::call_once(). Am I missing something here? Did I build it right or is there still something else I need to do to make it happy about stdlib?

I realize that my branch breaks the gnu-libc build by adding 'alpine' to the target in the makefile so if I do get this working I will be fixing that!

Steps to reproduce:

Open current folder in the provided ubuntu dev container (you will have to swap what's in .devcontainer/ with .devcontainer/ubuntu
From the VSCode terminal run make -f Unix/Makefile
Swap back to Alpine (replace .devcontainer/ with .devcontainer/alpine
run dotnet run --project ./MuslTest/MuslTest.csproj

ClearScriptLib · 2022-01-10T15:45:24Z

Hi @William-Froelich,

Quick question about your diff: You're defining CXXALPINEFLAGS, but where is that symbol used?

Thanks!

William-Froelich · 2022-01-10T16:27:17Z

It's not being used. I had originally added it because I thought it would be necessary, since it was in most of the examples I found. However, as far as I can tell, the --sysroot flag is only needed when you have musl in a non-standard install location such as when you download musl-gcc and other tools and compile them from source.

Nikolay-Ch · 2024-05-08T08:58:14Z

Hi,
Is there any information about this issue?
I have alpine docker image and get errors:

can't run Unable to load shared library '/app/runtimes/linux-x64/native/ClearScriptV8.linux-x64.so

ClearScriptLib · 2024-05-08T14:42:43Z

Hi @Nikolay-Ch,

Unfortunately, we have no update. Support for musl-based Linux platforms is still something we'd like to add in the future.

Good luck!

misaya · 2024-08-14T11:13:01Z

Has this issue been updated recently ? @Nikolay-Ch

ngoclamnn · 2024-09-23T01:24:05Z

no update after 3 years...Maybe people prefer to use Debian image. The debian one is working well: mcr.microsoft.com/dotnet/aspnet:8.0

Baklap4 · 2024-12-19T09:05:26Z

Any update for alpine linux? we're now at alpine 3.20 but it still doesn't work

A compilation step encountered an exception During loading of Sass compiler error has occurred. Failed to create instance of the V8JsEngine. Most likely it happened, because the 'ClearScriptV8.linux-x64.so' assembly or one of its dependencies was not found. Try to install the Microsoft.ClearScript.V8.Native.linux-x64 package via NuGet. with stacktrace:
     at DartSassHost.SassCompiler.InitializeCompiler()
     at DartSassHost.SassCompiler.CompileFile(String inputPath, String outputPath, String sourceMapPath, CompilationOptions options)
     at WebCompiler.Compile.SassCompiler.Compile(List`1 file_sequence) in /home/runner/work/WebCompiler/WebCompiler/WebCompiler/Compile/SassCompiler.cs:line 72
     at WebCompiler.Compile.CompilationStep.With(Compiler compiler) in /home/runner/work/WebCompiler/WebCompiler/WebCompiler/Compile/CompilationStep.cs:line 22
  
  The internal compiler SassCompiler encountered an exception: During loading of Sass compiler error has occurred. Failed to create instance of the V8JsEngine. Most likely it happened, because the 'ClearScriptV8.linux-x64.so' assembly or one of its dependencies was not found. Try to install the Microsoft.ClearScript.V8.Native.linux-x64 package via NuGet.. 
  The stacktrace was:
     at DartSassHost.SassCompiler.InitializeCompiler()
     at DartSassHost.SassCompiler.CompileFile(String inputPath, String outputPath, String sourceMapPath, CompilationOptions options)
     at WebCompiler.Compile.SassCompiler.Compile(List`1 file_sequence) in /home/runner/work/WebCompiler/WebCompiler/WebCompiler/Compile/SassCompiler.cs:line 72
     at WebCompiler.Compile.CompilationStep.With(Compiler compiler) in /home/runner/work/WebCompiler/WebCompiler/WebCompiler/Compile/CompilationStep.cs:line 22

SeanMsi changed the title ~~Error/Crasg when running in an Alpine Docker Image~~ Error/Crash when running in an Alpine Docker Image Dec 7, 2021

ClearScriptLib self-assigned this Dec 8, 2021

ClearScriptLib added the enhancement label Dec 8, 2021

ClearScriptLib changed the title ~~Error/Crash when running in an Alpine Docker Image~~ Add support for Alpine and other musl-based Linux distributions. Dec 8, 2021

ClearScriptLib changed the title ~~Add support for Alpine and other musl-based Linux distributions.~~ Add support for Alpine and other musl-based Linux distributions Dec 8, 2021

This was referenced Oct 5, 2022

Could not initialize class org.duckdb.DuckDBNative AlexR2D2/metabase_duckdb_driver#1

Open

Error loading shared library with DuckDB driver AlexR2D2/metabase_duckdb_driver#3

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add support for Alpine and other musl-based Linux distributions #331

Add support for Alpine and other musl-based Linux distributions #331

SeanMsi commented Dec 7, 2021 •

edited

Loading

ClearScriptLib commented Dec 8, 2021

William-Froelich commented Dec 18, 2021

William-Froelich commented Dec 18, 2021 •

edited

Loading

ClearScriptLib commented Dec 20, 2021

William-Froelich commented Jan 6, 2022

ClearScriptLib commented Jan 6, 2022

William-Froelich commented Jan 6, 2022

ClearScriptLib commented Jan 7, 2022

William-Froelich commented Jan 7, 2022 •

edited

Loading

ClearScriptLib commented Jan 10, 2022

William-Froelich commented Jan 10, 2022 •

edited

Loading

Nikolay-Ch commented May 8, 2024

ClearScriptLib commented May 8, 2024

misaya commented Aug 14, 2024

ngoclamnn commented Sep 23, 2024

Baklap4 commented Dec 19, 2024

Add support for Alpine and other musl-based Linux distributions #331

Add support for Alpine and other musl-based Linux distributions #331

Comments

SeanMsi commented Dec 7, 2021 • edited Loading

ClearScriptLib commented Dec 8, 2021

William-Froelich commented Dec 18, 2021

William-Froelich commented Dec 18, 2021 • edited Loading

ClearScriptLib commented Dec 20, 2021

William-Froelich commented Jan 6, 2022

ClearScriptLib commented Jan 6, 2022

William-Froelich commented Jan 6, 2022

ClearScriptLib commented Jan 7, 2022

William-Froelich commented Jan 7, 2022 • edited Loading

ClearScriptLib commented Jan 10, 2022

William-Froelich commented Jan 10, 2022 • edited Loading

Nikolay-Ch commented May 8, 2024

ClearScriptLib commented May 8, 2024

misaya commented Aug 14, 2024

ngoclamnn commented Sep 23, 2024

Baklap4 commented Dec 19, 2024

SeanMsi commented Dec 7, 2021 •

edited

Loading

William-Froelich commented Dec 18, 2021 •

edited

Loading

William-Froelich commented Jan 7, 2022 •

edited

Loading

William-Froelich commented Jan 10, 2022 •

edited

Loading