GRM-166: Fix docker-prune killing running molecule containers #273

Merged
kireto merged 1 commits from GRM-166-prune-running-containers into master 2026-09-15 14:19:02 +00:00
Member
No description provided.
kireto added 1 commit 2026-09-15 13:15:50 +00:00
fix: restrict docker-prune to exited containers
CI / validate (pull_request) Successful in 5m7s
CI / molecule-tests (1) (pull_request) Successful in 5m39s
CI / molecule-tests (4) (pull_request) Successful in 6m56s
CI / molecule-tests (2) (pull_request) Successful in 12m5s
CI / molecule-tests (3) (pull_request) Successful in 12m12s
CI / auto-merge (pull_request) Successful in 6m52s
3f1f3e3134
A stale molecule instance restarted by a new run still shows RunningFor
older than 1h, so the janitor force-removed it mid-converge
('No such container'). Only stopped containers are eligible now.
emil approved these changes 2026-09-15 13:16:22 +00:00
Dismissed
emil left a comment
Owner

Prune restricted to exited containers — fixes the stale-molecule-instance kill seen in infra nightly 5710.

Prune restricted to exited containers — fixes the stale-molecule-instance kill seen in infra nightly 5710.
emil approved these changes 2026-09-15 14:15:21 +00:00
emil left a comment
Owner

Auto-approved: all CI checks passed (validate, molecule-tests).

Auto-approved: all CI checks passed (validate, molecule-tests).
kireto merged commit 91635b5a5d into master 2026-09-15 14:19:02 +00:00
kireto deleted branch GRM-166-prune-running-containers 2026-09-15 14:19:02 +00:00
Sign in to join this conversation.