Skip to content

test: Set stop_signal to SIGTERM in nginx-based services#13881

Open
ricardobranco777 wants to merge 1 commit into
docker:mainfrom
ricardobranco777:nocore
Open

test: Set stop_signal to SIGTERM in nginx-based services#13881
ricardobranco777 wants to merge 1 commit into
docker:mainfrom
ricardobranco777:nocore

Conversation

@ricardobranco777

@ricardobranco777 ricardobranco777 commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

The official nginx images set STOPSIGNAL to SIGQUIT which dumps core. Set it to SIGTERM to avoid dumping core on e2e tests when containers running sleep infinity are stopped.

Mirrors similar fix done in #13214

What I did

Related issue

(not mandatory) A picture of a cute animal, if possible in relation to what you did

The official nginx images set STOPSIGNAL to SIGQUIT which dumps core.
Set it to SIGTERM to avoid dumping core on e2e tests when containers
running "sleep infinity" are stopped.

Signed-off-by: Ricardo Branco <rbranco@suse.de>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates an e2e watch fixture to stop nginx-based test containers with SIGTERM instead of inheriting the nginx image default STOPSIGNAL (SIGQUIT), which can generate core dumps during test teardown.

Changes:

  • Set stop_signal: SIGTERM for the backend service in pkg/e2e/fixtures/watch/rebuild-deps.yaml.
  • Set stop_signal: SIGTERM for the frontend service in the same fixture.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants