ci: switch to AWS container registry

[sampra2025]

As per AWS environment its recommended to use AWS Hosted docker hub instead of Public docker hub such as "docker.io", so updating the container registry.

[github-actions]

Test Results

 2 files  ±0   4 suites  ±0   6m 47s ⏱️ ±0s
15 tests ±0  15 ✅ ±0  0 💤 ±0  0 ❌ ±0 
38 runs  ±0  38 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 893ded3. ± Comparison against base commit 523802c.

♻️ This comment has been updated with latest results.

[github-actions]

Test jobs for commit c1ea40b

• Job 78195 on qcs6490
• Job 78196 on qrb2210-rb1

[doanac]

Github doesn't allow commenting on the commit message but that's the problem with this PR. You need a couple things:

• subject line
• body
• signed-off-by

So something more like:

ci: Switch to AWS container registry

The new CI workers are located in AWS and will benefit a little by using ECR.

Signed-off-by: .....

[github-actions]

Test jobs for commit c1ea40b

• Job 78225 on qcs6490
• Job 78224 on qrb2210-rb1

[github-actions]

Test jobs for commit 893ded3

• Job 78249 on qrb2210-rb1
• Job 78250 on qcs6490

[lool]

Hi, sorry just spotting this PR now; thanks Andy for your help in reviewing it!

I have no objection on the technical implementation, but I'd like to capture the specific reasons we're doing this change in this conversation or in the commit message.

You note in the PR message "As per AWS environment its recommended to use AWS Hosted docker hub instead of Public docker hub", and in the commit "The new CI workers are located in AWS and will benefit a little by using ECR".

Both sound like soft requirements and perhaps the latter hints at performance/costs benefits? Could you clarigy if we are doing this for security / best practices reasons from Qualcomm IT, for AWS cost/performance efficiency reasons, or for some other reasons?

I trust the registry will always mirror the latest debian:trixie images. Are all images available there and getting cached/audited somehow, or do I need to request new images I want to use? Is that the same process as for the Qualcomm internal container registry?

(BTW, I was wondering if you've considered implementing a github action that would check whether Qualcomm repositories have workflows that use the new runners and are not using the Elastic Container Registry; we do this to scan commits to make sure they have a signed-off-by and that it's not using a wrong email address for instance.)

[lool]

@sampra2025 Not sure you saw my comment above?