fix(docker): clear stale dind state on startup#7
Merged
Conversation
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
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
Incident context
Prod returned 502 after the host rebooted on 2026-07-08 19:47 UTC. nginx and the host were healthy, but main_sscan-nest never launched Nest because dockerd failed with:
failed to start daemon, ensure docker is not running or delete /var/run/docker.pid: process with PID 8 is still running
Manual prod recovery removed stale /var/run/docker.* state and restarted only main_sscan-nest; both api.sourcescan.dev and api-v2.sourcescan.dev returned 200 after that.
Verification
Note: local privileged docker:dind runtime test was not run because privileged dind on the workstation was blocked by safety policy.