Why is `biarch` image used for Arm64 glibc and not Alpine?

This seems odd and suggestive that one case is wrong.

https://github.com/dotnet/runtime/blob/333fb71d54bd84256e740aa08f8b836d4cd71d98/eng/pipelines/common/templates/pipeline-with-resources.yml#L29-L33

https://github.com/dotnet/runtime/blob/333fb71d54bd84256e740aa08f8b836d4cd71d98/eng/pipelines/common/templates/pipeline-with-resources.yml#L45-L48

This table doesn't list `biarch` but an Arm64 (glibc) image that looks like the Alpine one.

https://github.com/dotnet/runtime/blob/main/docs/workflow/building/coreclr/linux-instructions.md#docker-images

I'm guessing we need the biarch image for a specific scenario that doesn't apply to the actual product build and that the regular image would be fine for this case.

@sbomer 

	linux_arm64:
	image: mcr.microsoft.com/dotnet-buildtools/prereqs:cbl-mariner-2.0-cross-biarch-amd64-arm64
	env:
	ROOTFS_HOST_DIR: /crossrootfs/x64
	ROOTFS_DIR: /crossrootfs/arm64

	linux_musl_arm64:
	image: mcr.microsoft.com/dotnet-buildtools/prereqs:azurelinux-3.0-cross-arm64-alpine-net9.0
	env:
	ROOTFS_DIR: /crossrootfs/arm64

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Why is `biarch` image used for Arm64 glibc and not Alpine? #101707

richlander
openedon Apr 30, 2024

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Why is biarch image used for Arm64 glibc and not Alpine? #101707

Description

richlanderopenedon Apr 30, 2024

Metadata