Error unclear when there is a architectures mismatch with the runner and the docker image

If I run a job with a architecture mismatch. For example amd on a docker image that is arm based the error is unclear for why the failure is happening. It would be nice if we could make it clear that this is potential failure case, as the current error is unrelated to the shell.

Error Example:

Preparing environment
00:20
Using FF_USE_POD_ACTIVE_DEADLINE_SECONDS, the Pod activeDeadlineSeconds will be set to the job timeout: 1h0m0s...
WARNING: Advanced Pod Spec configuration enabled, merging the provided PodSpec to the generated one. This is a beta feature and is subject to change. Feedback is collected in this issue: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/29659 ...
Waiting for pod vt-firmware/runner-d7tc35u-project-3928-concurrent-4-2azylc8w to be running, status is Pending
ERROR: Job failed (system failure): prepare environment: setting up trapping scripts on emptyDir: unable to upgrade connection: container not found ("build"). Check https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading for more information