Verify prepared runtime IDs at launch (Refs #93)

2026-10-09 19:18:54 -04:00
parent 596b160be3
commit d1f581d6a8
5 changed files with 135 additions and 17 deletions
@@ -253,6 +253,12 @@ still run the configured default, but must update before accepting custom runtim
 Queued launches and migrations never trigger custom image pulls, and container
 creation cannot implicitly pull a missing image.

+Agent 1.8.7 also checks a runtime's current image ID against its recorded preparation
+before creating or rebuilding a container. If another program retags a prepared
+image, an admin must prepare it again from the host page before launching it.
+Containers are created using the validated immutable image ID, so a tag change
+after validation cannot substitute another image. Existing containers keep running.
+
 ### Resource samples and learned allowances

 Only provisioning reserves a host and port. Agent **1.4.6** fixes container