Docker containers fail to run on release/8.0.1xx

[NikolaMilosavljevic]

Error log

/usr/bin/docker logs --details b8f737412a7194ba7be552a8efb836e5fc63e998394ce2bb017190e860cc7dfb
 v20.19.4
 container-startup-using-node-20
/usr/bin/docker exec  b8f737412a7194ba7be552a8efb836e5fc63e998394ce2bb017190e860cc7dfb sh -c "command -v bash"
##[error]Docker-exec executed: `sh -c "command -v bash"`; container id: `b8f737412a7194ba7be552a8efb836e5fc63e998394ce2bb017190e860cc7dfb`; exit code: `128`; command output: `OCI runtime exec failed: exec failed: unable to start container process: procReady not received: unknown`

Image used: mcr.microsoft.com/dotnet-buildtools/prereqs:azurelinux-3.0-net8.0-cross-arm-alpine

Same image works fine in release/8.0.3xx builds - example

There is a difference between 8.0.1xx and 8.0.3xx. The former is using Ubuntu 20.04.6 host, the latter is using Ubuntu 22.04.5 host.

Notes

The issue exists for all legs using Linux containers - only on release/8.0.1xx.

[NikolaMilosavljevic]

@marcpopMSFT it seems that we need to update the host Linux OS in release/8.0.1xx to Ubuntu 22.04. This branch is still using Ubuntu 20.04. Will work on a PR.

[NikolaMilosavljevic]

Fixed with #20637