DOC-419/DOC-420: Document SIGILL crash on Apple Silicon and the supervisor's new fatal-signal diagnostics - #930
Open
quetzalliwrites wants to merge 2 commits into
Conversation
…ernels LocalStack Pro can exit immediately with exit code 252 (SIGILL) on newer Apple Silicon (e.g. M4) when running under Colima or Podman with an older Linux guest kernel, since the cryptography library (47.0.0+) uses ARM instructions those kernels don't fully support. Add the workaround (OPENSSL_armcap=0) and permanent fix (updating the guest kernel) to the startup troubleshooting FAQ, and cross-link it from the ARM64 support page's troubleshooting section. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
quetzalliwrites
requested review from
HarshCasper and
remotesynth
as code owners
September 9, 2026 19:03
Deploying localstack-docs with
|
| Latest commit: |
60da04b
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://37e6d5e4.localstack-docs.pages.dev |
| Branch Preview URL: | https://doc-419-localstack-pro-conta.localstack-docs.pages.dev |
Collaborator
Author
|
preview urls: @AntonLage 🐈⬛ |
The supervisor no longer crashes silently on a fatal signal (previously only visible with DEBUG=1): it now unconditionally logs the decoded signal name and exit code, and enables Python's faulthandler by default so native crashes print a stack trace pointing at the offending import. Update the Apple Silicon SIGILL FAQ entry (DOC-419) with the message users will now actually see, and the faulthandler opt-out via PYTHONFAULTHANDLER. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
quetzalliwrites
changed the title
|
LGTM! |
AntonLage
approved these changes
Sep 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents a user-reported issue and its follow-up fix:
252(SIGILL /-4in some supervisors). This is a known incompatibility between thecryptographylibrary (47.0.0+) and older Linux guest kernels running under Apple's Virtualization Framework — it mainly affects Colima or Podman with an older guest kernel; a fully updated Docker Desktop is generally not affected.DEBUG=1), and enables Python'sfaulthandlerby default so native crashes print a stack trace pointing at the offending code — for this scenario, directly at thecryptographyimport. Opt out withPYTHONFAULTHANDLER=0.Changes:
getting-started/faq.mdx) covering both: the decoded-signal message and faulthandler traceback users will now see, plus the workaround (OPENSSL_armcap=0, shown for both Docker Compose andlstk) and the permanent fix (updating the VM provider/guest kernel).Linear tickets
Test plan
npx astro buildcompletes successfully (417 pages built)