Skip to content

fix(supervise): scheduled prune no longer resets the idle clock (#496) - #533

Merged
zcsizmadia merged 1 commit into
mainfrom
fix/prune-via-engine-api
Oct 12, 2026
Merged

zcsizmadia merged 1 commit into
mainfrom
fix/prune-via-engine-api

Conversation

@zcsizmadia

Copy link
Copy Markdown
Collaborator

Fixes #496.

The scheduled prune ran docker through Skrog's own pipe, so each sweep counted as client activity. With prune.every <= idle-timeout the engine never idle-stopped.

  • prune.RunAPI: the same Plan, executed against the engine API (/containers|images|volumes|build/prune), with unit tests incl. volume/until parity with the CLI plan
  • engineClient shared with busyProbe: dials over the bridge transport, not the pipe server
  • skrog prune by hand is unchanged (CLI)
  • removed the prune-idle doctor check and the housekeeping.md caveat; CHANGELOG entry added

Not verified against a live engine yet.

… longer resets the idle clock (#496)

The prune ran docker through Skrog's own pipe, which stamped LastActivity;
a prune.every at or below idle-timeout kept the engine from ever idling.
prune.RunAPI executes the same plan against /containers, /images, /volumes
and /build prune over the bridge's own transport (shared with the busy
probe as engineClient). skrog prune by hand still uses the CLI.

The doctor check for the combination is removed: it is no longer a problem.
@zcsizmadia
zcsizmadia merged commit 84204f4 into main Oct 12, 2026
7 checks passed
@zcsizmadia
zcsizmadia deleted the fix/prune-via-engine-api branch October 12, 2026 13:41
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.

the automatic prune stamps LastActivity, so a short prune.every prevents idle-stop

1 participant