Bug: Linux durable functions emulator binary links to host zlib, causing issues for downstream packagers

[chenrui333]

Description:

The AWS SAM CLI wheel for Linux includes a prebuilt native binary:

samcli/local/rapid/aws-durable-execution-emulator-<arch>

which caused some downstream linkage issue

Full linkage --test aws-sam-cli output
  Unwanted system libraries:
    /lib/x86_64-linux-gnu/libz.so.1

/lib/aarch64-linux-gnu/libz.so.1
  libexec/lib/python3.13/site-packages/samcli/local/rapid/aws-durable-execution-emulator-arm64

relates to

• aws-sam-cli 1.150.0 Homebrew/homebrew-core#256861
• aws-sam-cli 1.150.1 Homebrew/homebrew-core#256993
• fix: build durable emulator image and copy binary to it #8484

[vicheey]

Do you mind providing additional information about how to reproduce the issue?

[valerena]

What's exactly the problem here? This binary is included in SAM CLI, but it's always used inside a Linux container. it's not supposed to be used directly in a Mac environment. In practice the Mac environment just reads it as a "file" that it's copied inside a container, not meant to be directly executed.

Can those files be kept normally in the brew artifacts as-is?

[daeho-ro]

It's not about MacOS. On linux host, the included binaries are linked to the system library libz.so that is unwanted in homebrew.

[chenrui333]

@valerena also is the emulator open source so that we can build from source code?

[roger-zhangg]

Hi @daeho-ro @chenrui333 we are planning to remove this durable function emulator from this package in the future release. It should solve this issue automatically.

[chenrui333]

That sounds great, would that mean people need to install the emulator separately?

[chenrui333]

@roger-zhangg and folks, any update on this thread?

we (homebrew) found some workaround via Homebrew/homebrew-core#262038

[alejandro-cedeno-10]

x2, any update this thread?

[valerena]

We're looking into the options to do this. The intention is to have a separate pre-built image with this binary instead of including it in SAM CLI. We don't have a specific timeline in mind yet, so we can't say when this be solved. But we will be communicating the progress here.