ECS Exit code: 132 on Graviton3

I running my app written in Rust on ECS backed by Graviton3 EC2. It runs as expected.

After my attempt to optimize compilation using processor specific things RUSTFLAGS="-C target-cpu=neoverse-v1 -C target-feature=+sve2,+lse" the app starts even prints some Wellcome output and stops with Exit code: 132.

I started separate EC2 with Graviton3 processor. Installed Docker there and same app with same dokerfile works there like a charm.

Is there som additional tuning required to use +sve2,+lse on ECS?