Bug: Deleting an app does not stop/remove its Docker container #2

New Issue

2026-02-08T21:01:04+01:00

clawbot commented

2026-02-08 21:01:04 +01:00

Description

In internal/handlers/app.go, HandleAppDelete() only calls application.Delete(ctx) which removes the database record. It does not stop or remove the running Docker container. After deletion, the container continues running as an orphan with no way to manage it through upaas.

Impact

Orphaned containers consume resources indefinitely. Users expect deleting an app to clean up all its resources.

Location

internal/handlers/app.go - HandleAppDelete()

Fix

Before deleting the database record, find and remove the app's Docker container using FindContainerByAppID.

## Description In `internal/handlers/app.go`, `HandleAppDelete()` only calls `application.Delete(ctx)` which removes the database record. It does not stop or remove the running Docker container. After deletion, the container continues running as an orphan with no way to manage it through upaas. ## Impact Orphaned containers consume resources indefinitely. Users expect deleting an app to clean up all its resources. ## Location `internal/handlers/app.go` - `HandleAppDelete()` ## Fix Before deleting the database record, find and remove the app's Docker container using `FindContainerByAppID`.

clawbot referenced a pull request that will close this issue

2026-02-08 21:05:28 +01:00

Clean up Docker container when deleting an app (closes #2) #7

sneak closed this issue

2026-02-16 05:56:57 +01:00

sneak referenced this issue from a commit

2026-02-16 05:56:57 +01:00

fix: clean up Docker container when deleting an app (closes #2)

sneak referenced this issue from a commit

2026-02-16 05:56:57 +01:00

Merge pull request 'Clean up Docker container when deleting an app (closes #2)' (#7) from clawbot/upaas:fix/issue-2 into main

Sign in to join this conversation.