amayer1983/docksentry v2.17.5

2.17.5 — a start after a self-update could die

on GitHub

One crash, and three lines of documentation that were simply wrong.

Fixed

• Docksentry could refuse to start after a self-update. A stray line sent the startup banner a third time, from inside the one-shot migration that removes Docksentry's own name from the auto-update list — outside the block where that message is built. With both conditions true (own name still in the list, and a start right after a self-update) the name was never bound and the start died with UnboundLocalError, after the threads were up and before the bot listener came on.

  Reproduced on the released 2.17.4 image and confirmed fixed on the same fixture. It also takes less than it looks: the self-update check only asks whether the marker file exists, so a leftover or unreadable deferred_check.json is enough. Short of the crash, it sent the same banner twice to every non-Telegram channel.

Changed

• TZ is documented as Europe/Berlin, which is what the image actually sets. The README said UTC while docs/configuration.md said the truth — and every schedule, quiet-hours window and update window runs on that clock.
• The health check waits up to 600 seconds, not 30. The documented 30 was a different setting: the stability window after a container already looks healthy.
• The Web UI password is hashed with scrypt, not SHA-256 — and one supplied as WEB_PASSWORD is not hashed at all, because an environment variable is plain text by nature. Both documents claimed otherwise; one of them was the security document.