ThinkBackgammon: the upstream container build is broken, so we maintain our own

Does this affect playing the game?

No. ThinkBackgammon works normally — this is about how we build and update it, not how it runs.

What is wrong

The container image published by the upstream project does not start: the build succeeds, but the container fails immediately on launch. Because of that, ThinkBackgammon does not run an upstream image at all — we build and host our own instead.

Why that matters

It means updates to the game depend on our own build rather than simply pulling a new upstream release, and rebuilding from scratch requires re-deriving that workaround. It is a maintenance cost rather than a user-facing fault, but it is the reason this service is not on a standard upstream image like most others.

Why it is Upstream

The defect is in the project's own container definition. Reported upstream as quasoft/backgammonjs#27 — open since August 2020 with no maintainer response, though the project itself is still active. This post tracks it.