Update to use the cbl-mariner webassembly images.

[jkoritzinsky]

This is one of the last official build targets that we weren't already using CBL-Mariner to build with.

[ghost]

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This is one of the last official build targets that we weren't already using CBL-Mariner to build with.

Author:	jkoritzinsky
Assignees:	jkoritzinsky
Labels:	area-Infrastructure-libraries
Milestone:	-

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This is one of the last official build targets that we weren't already using CBL-Mariner to build with.

Author:	jkoritzinsky
Assignees:	jkoritzinsky
Labels:	arch-wasm, area-Infrastructure
Milestone:	-

[directhex]

These images are 100% borked right now, yes? I just tried to use them for ICU, and am getting Docker errors

[jkoritzinsky]

Guess I missed some of the AzDO requirements for the containers...

[jkoritzinsky]

/azp run runtime, dotnet-linker-tests, runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[jkoritzinsky]

The WASM legs build the apps on the build system, so the mono-aot-cross executable needs to be able to run on the Helix machines. Need to figure out the best way to handle this.

[radical]

mono-aot-cross: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /root/helix/work/workitem/e/dotnet-latest/packs/Microsoft.NETCore.App.Runtime.AOT.linux-x64.Cross.browser-wasm/8.0.0-ci/Sdk/../tools/mono-aot-cross)
mono-aot-cross: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /root/helix/work/workitem/e/dotnet-latest/packs/Microsoft.NETCore.App.Runtime.AOT.linux-x64.Cross.browser-wasm/8.0.0-ci/Sdk/../tools/mono-aot-cross)
mono-aot-cross: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /root/helix/work/workitem/e/dotnet-latest/packs/Microsoft.NETCore.App.Runtime.AOT.linux-x64.Cross.browser-wasm/8.0.0-ci/Sdk/../tools/mono-aot-cross)
mono-aot-cross: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /root/helix/work/workitem/e/dotnet-latest/packs/Microsoft.NETCore.App.Runtime.AOT.linux-x64.Cross.browser-wasm/8.0.0-ci/Sdk/../tools/mono-aot-cross)

mono-aot-cross is being built on the build machines with mariner, but then used on helix which is still running ubuntu 18.04 .

[directhex]

Those numbers don't line up, glibc 2.34 is not what Mariner-built stuff should be offering. Our Mariner build images have the Mariner base OS, and are SUPPOSED TO cross-compile against a target OS (Ubuntu 16.04 in most cases) in /crossrootfs. 2.34 is WAY newer than that, it's like Ubuntu 21.10 or something (or maybe even the Mariner base itself? As opposed to the crossroot?)

[jkoritzinsky]

It's the Mariner base image itself. The WASM build legs build the "cross" tools on the base image. We don't ship those components; we build them again in another leg to produce the "cross" tools built against the correct target rootfs. We only hit this problem because WASM uses mono-aot-cross to build tests on Helix machines. This was working beforehand because the image where we built wasm was the same or older base image as the image we run wasm tests on.

The solution (which I need to look into) is to build the cross tools like mono-aot-cross against the correct rootfs.

[carlossanlop]

Does this change need to be backported?

[jkoritzinsky]

We're still determining the plans for these infra changes for existing release branches.

[jkoritzinsky]

/azp run runtime, dotnet-linker-tests, runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[jkoritzinsky]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jkoritzinsky]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jkoritzinsky]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jkoritzinsky]

Failures are either known or #86533

[lewing]

The official build started failing after this https://dev.azure.com/dnceng/internal/_build/results?buildId=2197698&view=logs&j=f5dc5c25-a228-5330-5793-27e0590c86b7&t=0577d8ca-da8f-5816-9616-b0711151fa80&l=1508

[jkoritzinsky]

I'm testing out a possible fix. Should have something by EOD today hopefully.