You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/v2-resource-plan.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,7 +72,7 @@ This document tracks the intended direction for DCP V2 resources. The current V2
72
72
-`PhysicalContainerImage` provides source image pull and build workflows.
73
73
-`PhysicalContainer` creates or tracks one runtime container, reports runtime status and port mappings, and references a same-namespace `PhysicalContainerImage`.
74
74
-`PhysicalContainerNetwork` creates or references one runtime container network and reports its observed identity, driver, and address allocations. Networks referenced by runtime ID are always retained. Created networks are retained when `persistent` is true; otherwise deletion enumerates running and stopped attachments, forcibly disconnects each container without removing it, and then removes the network. Name collisions are terminal unless `replaceExisting` is true, in which case the controller safely removes the specifically resolved network before creating its replacement. Runtime adapters classify their own built-in, non-removable networks, and replacement rejects them before disconnecting any attachments.
75
-
-`PhysicalContainerVolume` creates or tracks one runtime container volume and reports its observed name, driver, scope, mount point, and creation time. Unless persistent, deletion removes the volume after it is no longer referenced by a container. It deliberately does not use force removal: Docker still rejects in-use volumes, while Podman force removal deletes the containers using the volume. Created volumes carry creator and persistence labels, and startup harvesting removes abandoned non-persistent volumes after abandoned containers.
75
+
-`PhysicalContainerVolume` creates or references one runtime container volume and reports its observed name, driver, scope, mount point, and creation time. Volumes referenced by runtime ID are always retained. Created volumes are retained when `persistent` is true; otherwise deletion removes them after they are no longer referenced by a container. Name collisions are terminal unless `replaceExisting` is true, in which case the controller safely removes the specifically resolved volume before creating its replacement. Removal deliberately does not use force: Docker still rejects in-use volumes, while Podman force removal deletes the containers using the volume. Created volumes carry creator and persistence labels, and startup harvesting removes abandoned non-persistent volumes after abandoned containers.
76
76
- The physical resources use in-memory progress data, standardized `Ready` conditions, and queued work where side effects can block.
err=errors.Join(err, errors.Join(containers.ErrIncomplete, fmt.Errorf("not all volumes were removed, expected %d but got %d", len(options.Volumes), len(removed))))
0 commit comments