Every deploy leaves an anonymous Docker volume behind from the git clone container #215

New Issue

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

clawbot commented

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

Every deploy leaves an unused anonymous Docker volume behind.

The clone step runs the pinned alpine/git image, and that image declares a volume at /git, so Docker creates an anonymous volume for each clone container. upaas removes the clone container without asking Docker to remove its volumes (ContainerRemove with only Force: true, in internal/docker/client.go), so the volume stays. Found in the rehearsal for #213: five deploys left five anonymous volumes, each created at the second its deploy started. On a long-running host they pile up with every push.

Definition of done

A deploy leaves no Docker volume behind once it finishes, whether it succeeds or fails. For example, the clone container is removed together with its anonymous volumes.
A test or a documented manual check shows that the Docker volume list is the same before and after a deploy.

Model: opus-5-5

Every deploy leaves an unused anonymous Docker volume behind. The clone step runs the pinned `alpine/git` image, and that image declares a volume at `/git`, so Docker creates an anonymous volume for each clone container. upaas removes the clone container without asking Docker to remove its volumes (`ContainerRemove` with only `Force: true`, in `internal/docker/client.go`), so the volume stays. Found in the rehearsal for https://git.eeqj.de/sneak/upaas/issues/213: five deploys left five anonymous volumes, each created at the second its deploy started. On a long-running host they pile up with every push. ## Definition of done - A deploy leaves no Docker volume behind once it finishes, whether it succeeds or fails. For example, the clone container is removed together with its anonymous volumes. - A test or a documented manual check shows that the Docker volume list is the same before and 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 this issue from a commit

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

Remove the git clone container's anonymous volume with it (closes #215)

clawbot referenced a pull request that will close this issue

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

Remove the git clone container's anonymous volume with it (closes #215) #217

clawbot commented

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

Fixed in #217: the clone container is now removed together with its anonymous volume, whether the clone succeeds or fails, with a test against a fake Docker API.

Model: opus-5-5

Fixed in https://git.eeqj.de/sneak/upaas/pulls/217: the clone container is now removed together with its anonymous volume, whether the clone succeeds or fails, with a test against a fake Docker API. Model: opus-5-5

clawbot referenced this issue

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

Remove the git clone container's anonymous volume with it (closes #215) #217

clawbot referenced this issue from a commit

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

Remove the clone container even when the deploy is cancelled (closes #215)

clawbot referenced this issue

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

Remove the git clone container's anonymous volume with it (closes #215) #217

clawbot referenced this issue from a commit

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

Remove the git clone container's anonymous volume with it (closes #215)