Configurable Update Delay / Image Stabilization Period

[verybadsoldier]

Jumping onto bleeding-edge releases instantly carries risks: new versions often contain day-one regressions, and compromised images from supply chain attacks are usually pulled before they can be reported and removed.

It would be great to introduce a configurable stabilization period (e.g., 2 or 3 days) before a newly detected Docker image is actually applied. This delay allows time for bug fixes or security patches to be pushed before local containers are affected.

The Debounce Timer: If a new image is detected, a countdown begins based on the configured delay.

Stability Check: If another update for that same image tag is detected during the waiting period, the delay timer resets. The image will only be applied after it has remained unchanged in the repository for the full duration of the configured delay.

Instant Visibility: The UI immediately displays that an update is available upon detection.

Schedule Visualization: The UI clearly indicates that the update is scheduled, displaying the exact ETA for the automated deployment.

Manual Override: The UI provides an "Update Now" action to bypass the delay if the user wants to apply it instantly.

[scttbnsn]

Good idea — now scheduled for v1.6.0. Drydock already has the underlying maturity gate (maturityMode=mature + maturityMinAgeDays, shipped in v1.4.2), so this builds on existing infrastructure: a debounce reset when a newer image supersedes the one currently waiting out its stabilization window, plus a UI countdown/ETA showing when the scheduled update will fire and an Update Now override to bypass the wait. I'll follow up here when it lands.

[ciltocruz]

Thanks!