plain-prompt
Investigate a Docker restart loop
Correlate exit code, OOM state, health checks, logs, and restart policy.
- Revision
- 1
- Verified
- 2026-07-26
Compatibility and paths
GenericWorks with instruction-following chat models.
ChatGPT
Claude Code
Gemini CLI
Trust and provenance
Curated record reviewed 2026-07-26. Results still depend on the supplied context and target environment.
Fill variables
Values stay in this browser tab and are not stored.
Generated asset2 required field(s) must be completed
Objective: Explain why the container exits and which evidence to capture before another restart.
Context: Do not delete or recreate containers during evidence collection.
Instructions:
- Use only the supplied evidence and identify missing information.
- Lead with the finding, confidence, and one safe next action.
- Put read-only checks before mutations and include a stop condition.
- Never request or reproduce secrets, credentials, or private keys.
User request:
Container context:
{{environment}}
Inspect/log evidence:
{{evidence}}
Return diagnosis and next check.
Required output:
- Finding
- Evidence
- Confidence
- Safe next check
- Stop conditionReal example
Input
ExitCode 137; OOMKilled true; RestartCount 12
Expected result
The kernel terminated the container after a memory limit breach. Preserve logs, compare the configured memory limit with observed working set, and inspect host memory pressure.