fix: correct LocalStack status after Lambda invocation#7
Merged
Conversation
LocalStack’s status tracker was incorrectly reporting the main container as stopped after invoking a Lambda function. This happened because `docker events --filter container=localstack-main` matches any container whose name starts with `localstack-main`, including temporary Lambda containers (e.g., `localstack-main-<hash>`). As a result, the tracker picked up stop events for these Lambda containers instead of the main one, leading to false status reports. This commit updates the filter logic to ensure only the main container’s events are tracked.
Merged
tiurin
added a commit
that referenced
this pull request
Sep 2, 2025
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.
LocalStack’s status tracker was incorrectly reporting the main container as stopped after invoking a Lambda function. This happened because
docker events --filter container=localstack-mainmatches any container whose name starts with localstack-main, including temporary Lambda containers (e.g., localstack-main-<hash>). As a result, the tracker picked up stop events for these Lambda containers instead of the main one, leading to false status reports. This commit updates the filter logic to ensure only the main container’s events are tracked.