Docker container is killed partway through creating a readaloud, with no error in the logs

Self-hosting Storyteller in Docker Desktop on a 16 GB machine. Every time I try to sync an audiobook with an ebook, the container stops on its own. The logs show nothing except the container stopping — no stack trace. It used to work; nothing obvious changed except that it has been a while since I last created a readaloud.

Resolution: A container that dies silently mid-processing, with empty logs or a code 127, has almost always been OOM-killed — transcription holds a whole audio track in memory, so peak usage scales with track length, and a single long M4B track can blow past the limit even though shorter books worked before. The quickest fix is to lower the maximum track length in Storyteller's own settings (try 45 or 30 minutes), which splits the audio into smaller units and cuts peak memory sharply. Also raise the memory limit given to the container — in Docker Desktop this is in the resources settings, and it is capped well below your physical RAM by default, which is why a 16 GB machine still runs out. Buying more RAM is not the answer here; the default track length and the Docker memory cap are.