Container identity and runtime state
Keep an image digest separate from writable files, runtime options and loaded model state.
Research note · November 14, 2026Research question
What does identifying a container image leave outside the release record?
Method
- Record the immutable image descriptor and the container’s runtime configuration. Inventory model files supplied through mounts or downloaded after startup rather than assuming they are included in the image.
- Run the same image with two different mounted model folders. Compare image identity, file identity and reported loaded identity as three independent observations.
- Include memory and CPU limits when evaluating runtime behavior. Preserve the image digest even when a mutable tag is used to request startup.
Records to retain
- Image digest and descriptor
- Mounted or fetched model identities
- Container resource limits
- Reported runtime state
Source basis
OCI descriptors identify content objects, while Docker resource constraints govern execution conditions. Neither image identity nor a resource limit alone describes every mutable dependency consumed by a running process.
Interpretation & limits
This method does not establish container isolation as a sufficient security boundary. A host compromise or unrecorded mount can invalidate assumptions. No Contour container adapter is claimed.
Next experiments
- Construct a same-image, different-model fixture pair.
- Record which startup dependencies remain mutable.
References
Technical reference
Implementation details supporting this note, drawn directly from the maintained documentation. These are technical references, not additional papers or new experimental results. Expand a topic to inspect its method, fields and limits.