Newest JSII image has corrupted AWS CLI

[biffgaut]

Describe the bug

Open a new container using latest image. Type the command:

aws s3 ls

Result is :

rosetta error: failed to open elf at /lib64/ld-linux-x86-64.so.2
 Trace/breakpoint trap

(image is authenticated with Access Key and Session token in environment variables)

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

A list of buckets in the authenticated account

Current Behavior

rosetta error: failed to open elf at /lib64/ld-linux-x86-64.so.2
Trace/breakpoint trap

Reproduction Steps

Authenticate environment

aws s3 ls

Possible Solution

A quick search of the error message on the web suggests the issue could be an x86/arm mix up issue.

Additional Information/Context

Image Info:
public.ecr.aws/jsii/superchain
1-bookworm-slim
sha256:e36c4b9d76a7712f31fea38b587da511cd9bb92386a8bebec55763831d0bd346
f05f7edf15b5
2 days ago
4.65GB

It appears this may also have been an issue in: sha256:9ff38d9c44e10394e7c7bd242c265fc8af856a7d5b49607f6351db4828b2a37

I'm reasonably certain this has worked in the past - the CLI is installed as it attempts to run and then fails. This is the simplest symptom to isolate - the problems initially manifested when our long time scripts using integ-runner started failing with odd missing module errors.

SDK version used

N/A

Environment details (OS name and version, etc.)

Full image info shown above

[biffgaut]

I've gotten the SHA for some older images and this has been consistent behavior for a while and now appears unrelated to issues I saw running integ-runner recently. I'll close this. If I can demonstrate an issue running integ-runner that is newly introduced I'll open a new Issue. Thanks.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.