Add Ubuntu 24.04 "noble" images

[lbussell]

• Added Noble images to 8.0
• Replaced Jammy with Noble for 9.0 preview

We also needed a new solution for the AOT cross Dockerfiles since Ubuntu 24.04 is changing to the DEB822 standard for package source lists: https://manpages.debian.org/stretch/apt/sources.list.5.en.html

Related: #5181

[richlander]

FYI @baronfel

[lbussell]

I was not able to reproduce the previous arm32 permissions issues locally today so we'll see if it passes PR validation this time.

[lbussell]

Removed Noble arm32 images due to https://bugs.launchpad.net/ubuntu/+source/tar/+bug/2059734.

[lbussell]

Filed #5319 to follow-up on the arm32 issue.

[lbussell]

Current issue: Noble package repos are undergoing a huge re-build since the compromised versions of liblzma and xz-utils were in the build environment of every package built since February 26. Not all packages are re-built yet so that's why we're getting unresolvable dependencies. We should continue retrying a couple times a day until all of our dependencies are available. Source

[lbussell]

According to the Noble release schedule, it's probably best to wait until the Beta release date (2024-04-11) to merge these images.

[lbussell]

Current issue - the Chisel tool isn't able to install some packages from the archive:

• libdb5.3 slice broken in ubuntu-24.04 canonical/chisel-releases#216

[richlander]

I'm glad we're catching these issues early. Our support for Ubuntu has become more complex, so the early work is definitely warranted.

[lbussell]

The Noble arm32 SDK image is going to take additional work to work around the tar arm32 issue, since it isn't yet multi-stage. https://github.com/dotnet/dotnet-docker/pull/5241/files#diff-9f4ce0ee04bfb6f01b0ba93e25a9b6a5eaef983ab2b50d7791dc1c7dafa29a85

[mthalman]

@lbussell - Looks like Dockerfiles need to be regenerated.

[lbussell]

The issue is that we can't establish an SSL connection to our NuGet feeds due to a NotTimeValid issue with the certs. This is probably due to the t64 migration. I am doing some additional investigation to determine where/if we need to respond to this in .NET.

 #10 2.041 info : X.509 certificate chain validation will use the fallback certificate bundle at '/usr/share/dotnet/sdk/9.0.100-preview.4.24221.5/trustedroots/codesignctl.pem'.
 #10 2.129 info : X.509 certificate chain validation will use the fallback certificate bundle at '/usr/share/dotnet/sdk/9.0.100-preview.4.24221.5/trustedroots/timestampctl.pem'.
 #10 2.133 info : Adding PackageReference for package 'foo' into project '/source/app/app.csproj'.
 #10 8.469 error: Unable to load the service index for source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public/nuget/v3/index.json.
 #10 8.469 error:   The SSL connection could not be established, see inner exception.
 #10 8.469 error:   The remote certificate is invalid because of errors in the certificate chain: NotTimeValid

[lbussell]

Filed dotnet/runtime#101444 for the arm32 issue.

[richlander]

Woohoo!