-
Notifications
You must be signed in to change notification settings - Fork 6
Deleting a container that still exists in the DB, but not in youki, fails #103
Copy link
Copy link
Open
Labels
area/operatingsystemOperating system-related concerns.Operating system-related concerns.
Description
The deletion fails and the container stays in the database.
Example:
$ feos-cli container list
CONTAINER_ID STATE IMAGE_REF
-------------------------------------- --------------- ----------------------------------------
b98b86c4-9e23-43a8-add8-8de8157b1310 Stopped <image-ref>
$ feos-cli container delete b98b86c4-9e23-43a8-add8-8de8157b1310
Requesting to delete container: b98b86c4-9e23-43a8-add8-8de8157b1310...
Error: status: Internal, message: "Runtime adapter error: Task service communication failed: status: NotFound, message: \"b98b86c4-9e23-43a8-add8-8de8157b1310\", details: [], metadata: MetadataMap { headers: {\"content-type\": \"application/grpc\", \"date\": \"Tue, 30 Dec 2025 13:56:52 GMT\"} }", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Tue, 30 Dec 2025 13:56:52 GMT"} }
$ feos-cli container list
CONTAINER_ID STATE IMAGE_REF
-------------------------------------- --------------- ----------------------------------------
b98b86c4-9e23-43a8-add8-8de8157b1310 Stopped <image-ref>
Desired Behavior
Whatever the reason why the container does not exist in youki anymore, the delete command should still delete the container from the database to clean up the state. The result can contain a warning that the underlying container did not exist anymore. It might still return a NotFound error.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/operatingsystemOperating system-related concerns.Operating system-related concerns.
Type
Projects
Status
No status