Add Dockerfiles for alpine3.18

[lbussell]

Fixes #4607

Release issue: https://github.com/dotnet/release/issues/541

[MichaelSimons]

The 7.0-alpine-arm64v8 floating tag should stay pointing to alpine 3.17

[MichaelSimons]

Looks like the 7.0-alpine-arm64v8 tag was dropped.

[MichaelSimons]

Looks like the 7.0-alpine-arm32v7 tag was dropped.

[MichaelSimons]

Looks like the 7.0-alpine-arm64v8 tag was dropped.

[mthalman]

3.18 should be listed above 3.17. Applies in all instances.

[mthalman]

This requires regenerating the readmes.

[mthalman]

Looks like there's a PowerShell failure in 6.0 that needs to be investigated. Seems consistent.

[lbussell]

@jander-msft, when do we want to move monitor to alpine3.18? Sometime after these are released and you have time to test it?

[jander-msft]

@jander-msft, when do we want to move monitor to alpine3.18? Sometime after these are released and you have time to test it?

It should move to 3.18 when the floating alpine tags are moved to 3.18

[jander-msft]

@jander-msft, when do we want to move monitor to alpine3.18? Sometime after these are released and you have time to test it?

It should move to 3.18 when the floating alpine tags are moved to 3.18

Completely separate from this effort to add the 3.18, I would like to somehow codify that .NET Monitor should move with the floating tags in the manifest and dockerfiles such that we don't have to think about it, but I haven't worked that out yet. We did briefly discuss this earlier this year, and it might require a new set of floating tags. I can log an issue about this where it can ideated before executing on it.

[lbussell]

The issue here looks similar to PowerShell/PowerShell#19679 but with a different type initializer: System.Management.Automation.TypeAccelerators vs. System.Management.Automation.PSVersionInfo.

System.InvalidOperationException : Failed to execute docker run --name 6.0-pwsh-133292649288916909 --rm  mcr.microsoft.com/dotnet/nightly/sdk:6.0-alpine3.18-amd64 pwsh -c (Get-Childitem env:DOTNET_RUNNING_IN_CONTAINER).Value
Exit code: 139
Standard Error: One or more errors occurred. (The type initializer for 'System.Management.Automation.TypeAccelerators' threw an exception.)
Process terminated. The type initializer for 'System.Management.Automation.PSObject' threw an exception.
at System.Environment.FailFast(System.String, System.Exception)
at Microsoft.PowerShell.UnmanagedPSEntry.Start(System.String[], Int32)
at Microsoft.PowerShell.ManagedPSEntry.Main(System.String[])
System.TypeInitializationException: The type initializer for 'System.Management.Automation.PSObject' threw an exception.
---> System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Management.Infrastructure, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. The system cannot find the file specified.


File name: 'Microsoft.Management.Infrastructure, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
--- End of inner exception stack trace ---
at System.Management.Automation.PSObject.get_Properties()
at System.Management.Automation.HostUtilities.GetDollarProfile(String allUsersAllHosts, String allUsersCurrentHost, String currentUserAllHosts, String currentUserCurrentHost)
at Microsoft.PowerShell.ConsoleHost.DoRunspaceInitialization(Boolean skipProfiles, String initialCommand, String configurationName, Collection1 initialCommandArgs)    at Microsoft.PowerShell.ConsoleHost.DoCreateRunspace(String initialCommand, Boolean skipProfiles, Boolean staMode, String configurationName, Collection1 initialCommandArgs)
at Microsoft.PowerShell.ConsoleHost.CreateRunspace(Object runspaceCreationArgs)
at Microsoft.PowerShell.ConsoleHost.DoRunspaceLoop(String initialCommand, Boolean skipProfiles, Collection`1 initialCommandArgs, Boolean staMode, String configurationName)
at Microsoft.PowerShell.ConsoleHost.Run(CommandLineParameterParser cpp, Boolean isPrestartWarned)
at Microsoft.PowerShell.ConsoleHost.Start(String bannerText, String helpText)
at Microsoft.PowerShell.UnmanagedPSEntry.Start(String[] args, Int32 argc)

[lbussell]

I think we'll need to wait on dotnet/runtime#86284 to flow through. It might already be in the nightly builds but since #4628 is blocked, I'm not sure yet.

There's also a full release checklist here: dotnet/core#8470

[mthalman]

It might already be in the nightly builds but since #4628 is blocked, I'm not sure yet.

Since this is 6.0, it wouldn't be there until the June servicing release.

[lbussell]

I filed PowerShell/PowerShell#19703.

Since this is 6.0, it wouldn't be there until the June servicing release.

What's the resolution then? If the RID is the solution (which it may or may not be) would we have to wait until July to ship Alpine3.18 for 6.0? Or just validate internally ahead of time?

[mthalman]

What's the resolution then? If the RID is the solution (which it may or may not be) would we have to wait until July to ship Alpine3.18 for 6.0? Or just validate internally ahead of time?

Assuming the RID fixes the issue, then yes, we'd have to wait until July. We should be able to validate that in our internal branch now.

[lbussell]

An internal test run validated that the RID addition solves the PowerShell issue: https://dev.azure.com/dnceng/internal/_build/results?buildId=2187733&view=results (internal MSFT link)

[tvbishan]

@lbussell @mthalman So, we have to wait until July to receive Alpine 3.18 for 6.0?

[mthalman]

@lbussell @mthalman So, we have to wait until July to receive Alpine 3.18 for 6.0?

That hasn't been determined yet.

[mthalman]

We should constrain this further since it's working on everything except for 6.0.

Suggested change

	else if (imageData.OS.Contains("3.18"))
	else if (imageData.Version.Major == 6 && imageData.OS.Contains("3.18"))

[mthalman]

Suggested change

	reason = "Powershell does not support Alpine 3.18 yet, skip testing"
	reason = "Powershell does not support Alpine 3.18 yet, skip testing";

[mthalman]

Looks like the Dockerfiles need to be regenerated.