Binary execution issues in SAM CLI container due to read-only file system #7469
Labels
blocked/more-info-needed
More info is needed from the requester. If no response in 14 days, it will become stale.
We've encountered a recent change in behavior when executing binaries within the SAM CLI container environment. Previously, we were able to execute a binary from within our project's directory hierarchy without issue. However, we're now experiencing a "read-only file system" error which prevents the binary from running unless it is placed in the
/tmp
directory.This change is significantly impacting our development workflow. Moving the binary to
/tmp
requires us to rebuild the container on every code change, rather than just updating the code and re-invoking the lambda, which was possible before.Steps to reproduce
Observed result
The binary cannot execute unless it's placed in
/tmp
, due to the read-only file system error.Expected result
The binary should be executable within the project directory hierarchy, as it was previously.
Currently our workaround is to create a dockerfile with the binary copied to /tmp and it works but as i wrote each code change requires building and its slowing the work
Thank you for your support.
The text was updated successfully, but these errors were encountered: