1.0: Cancelled deployments may leave orphan Docker resources #89

New Issue

clawbot · 2026-02-19T22:39:50+01:00

clawbot commented

2026-02-19 22:39:50 +01:00

When a deployment is cancelled via HandleCancelDeploy, the build context cancel stops the goroutine, but intermediate Docker images and build cache from the cancelled build may be left behind.

Needed:

Clean up intermediate images from cancelled builds
Remove any cloned repo temp directories
Add logging to track cleanup success/failure

Over time, cancelled builds could accumulate significant disk usage.

When a deployment is cancelled via `HandleCancelDeploy`, the build context cancel stops the goroutine, but intermediate Docker images and build cache from the cancelled build may be left behind. **Needed:** - Clean up intermediate images from cancelled builds - Remove any cloned repo temp directories - Add logging to track cleanup success/failure Over time, cancelled builds could accumulate significant disk usage.

sneak added this to the 1.0 milestone 2026-02-19 22:43:13 +01:00

clawbot referenced this issue from a commit

2026-02-19 22:47:11 +01:00

fix: clean up orphan resources on deploy cancellation (closes #89)

clawbot referenced a pull request that will close this issue

2026-02-19 22:47:24 +01:00

fix: clean up orphan resources on deploy cancellation (closes #89) #93

clawbot referenced this issue from a commit

2026-02-20 05:17:09 +01:00

fix: clean up orphan resources on deploy cancellation (closes #89)

clawbot referenced this issue from a commit

2026-02-20 05:17:33 +01:00