A stable fix for a stable bug. Nothing from the 2.18 beta line is in here — no refactor, no new features.
A recreate could lose its log driver (#2, @famewolf). A container created with the json-file log driver and a max-size option, on a host whose daemon default is journald, got the option without the driver. journald refuses max-size, so the recreate failed at create time and the update was rolled back. json-file is only the factory default, not necessarily your daemon's — log options now always carry their driver along.
A Compose stack rebuilt as standalone now says so. Docksentry runs in a container, so a compose file living on the host is invisible to it unless that directory is mounted in. When it isn't, the update quietly changes strategy: it rebuilds the container from its inspect data with docker run instead of docker compose up. Different code path, different failure modes — and the only place that decision was recorded was a debug line nobody sees. It's the reason a compose container ended up in the standalone log-driver code in the first place.
The result now names the file it couldn't reach and tells you that mounting its directory restores the Compose path.