Images from earlier deploys are never removed, so disk use grows with every deploy #216

New Issue

2026-09-23T11:00:11+02:00

clawbot commented

2026-09-23 11:00:11 +02:00

Images from earlier deploys are never removed, so disk use grows with every deploy.

Each deploy builds and tags a new image (upaas-<app>:<deployment number>). upaas removes an image only when a deploy is cancelled (internal/service/deploy/deploy.go). After five deploys of homoicon in the rehearsal for #213, all five tags were still present, plus about 20 untagged intermediate build images per deploy. Nothing removes them. On fsn1app1 every push adds a full image and its build layers until the disk fills.

Definition of done

After a successful deploy, upaas removes app images that neither the running container nor a rollback can use. It keeps the image rollback needs, if any.
The intermediate images a build leaves behind are removed too, or the PR explains why they must stay.
A test covers which images are kept and which are removed after a deploy.

Model: opus-5-5

Images from earlier deploys are never removed, so disk use grows with every deploy. Each deploy builds and tags a new image (`upaas-<app>:<deployment number>`). upaas removes an image only when a deploy is cancelled (`internal/service/deploy/deploy.go`). After five deploys of homoicon in the rehearsal for https://git.eeqj.de/sneak/upaas/issues/213, all five tags were still present, plus about 20 untagged intermediate build images per deploy. Nothing removes them. On fsn1app1 every push adds a full image and its build layers until the disk fills. ## Definition of done - After a successful deploy, upaas removes app images that neither the running container nor a rollback can use. It keeps the image rollback needs, if any. - The intermediate images a build leaves behind are removed too, or the PR explains why they must stay. - A test covers which images are kept and which are removed after a deploy. Model: opus-5-5

clawbot referenced this issue

2026-09-23 11:01:18 +02:00

Rehearse the fsn1app1 deploy on the build host with homoicon as the app #213

clawbot referenced this issue

2026-09-23 11:01:26 +02:00

Deploy µPaaS to fsn1app1 and verify end-to-end #181

clawbot referenced a pull request that will close this issue

2026-09-23 11:50:54 +02:00

Remove images from earlier deploys after a successful deploy #219

clawbot referenced this issue from a commit

2026-09-23 11:50:56 +02:00

Remove images from earlier deploys after a successful deploy (closes #216)

clawbot commented

2026-09-23 11:51:02 +02:00

Built in #219: after a successful deploy, images other than the running one and the one rollback uses are removed, with the untagged images of their final build stage. Leftovers of other build stages stay; the PR explains why.

Model: opus-5-5

Built in https://git.eeqj.de/sneak/upaas/pulls/219: after a successful deploy, images other than the running one and the one rollback uses are removed, with the untagged images of their final build stage. Leftovers of other build stages stay; the PR explains why. Model: opus-5-5

clawbot referenced this issue from a commit

2026-09-23 12:09:49 +02:00

Remove images from earlier deploys after a successful deploy (closes #216)

clawbot referenced this issue from a commit

2026-09-23 12:09:49 +02:00

Remove old images by tag, and test the step after a deploy (closes #216)

clawbot closed this issue

2026-09-23 12:24:36 +02:00

clawbot referenced this issue from a commit

2026-09-23 12:24:36 +02:00

Remove images from earlier deploys after a successful deploy (closes #216)

Sign in to join this conversation.