14.8 Container Cleanup [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 14.8 Container Cleanup ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:14-containerisation:start | Return to Containerisation ]]

Container cleanup should remove temporary runtime [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] without destroying source files, generated Artifacts, [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] Configuration, logs, or acceptance [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] unless the user explicitly requests that action.

The team should distinguish:

  - Stopping containers.
  - Removing stopped containers.
  - Removing temporary networks.
  - Removing temporary volumes.
  - Removing build cache.
  - Removing generated runtime outputs.
  - Removing logs or Evidence.

The ''stopAll.sh'' script should stop the Node network. A separate cleanup command or script may remove temporary runtime Artifacts after the team has preserved required logs and Evidence.

Cleanup actions should be explicit. A script should not delete logs, Evidence, generated Artifacts, or local [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] as a side effect of stopping the system. If the team provides a destructive cleanup option, the script should clearly name it, document it, and require deliberate user action.

Container cleanup should support repeatable reruns. After cleanup, a developer should be able to rebuild containers, rerun the Node network, collect new logs, and compare Evidence without leftover runtime state causing misleading results.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>