Fixed
A compose update that pulls the new image but keeps running the old one is no longer reported as success (#35, reported by @NotRetarded).
The compose path ran docker compose up -d --no-deps, which can leave the existing container (and old image) in place if Compose judges the service "unchanged" — so the freshly-pulled image never gets loaded, yet the update reported OK. Two changes:
- the recreate now uses
--force-recreateso the container is actually replaced; - after it comes up, Docksentry compares the running container's image ID against the pulled image's ID — a mismatch is reported as a failure with a clear message instead of a phantom success.