Fixed
/check during an ongoing update no longer reports in-flight containers as available
Closes #26. Reported by @famewolf.
While run_updates() was processing 3 containers, hitting /check again would re-run check_all() — which still saw the two not-yet-recreated containers as on their pre-pull digest, so they'd appear in a second "Updates Available" notification ~30s after the user already tapped "Update all":
12:24:00 /check → 3 updates available
12:24:00 Update all → "Starting update for 3 containers..."
12:24:30 /check again → still shows 2 of those 3 as "available"
12:25:30 ✅ original update completes for all three
run_updates() was already single-instance protected (taps on the duplicate notification just returned "update already in progress" — no double-update risk), but the cosmetic confusion was real.
/check now honours the same update_running flag and returns "Update already in progress…" instead of re-running check_all(). Reuses the existing update_already_running i18n key — no new translations needed.
docker pull amayer1983/docksentry:latest
docker compose up -d