If Puppeteer disconnects in Docker with zero errors in the log, launch Chrome with the flag that disables the NetworkServiceInProcess2 feature. That was the maintainer's workaround for this silent-disconnect bug and the reporter confirmed it. One caveat from the thread: the flag can affect network interception features, so if you rely on request interception, test that path explicitly after applying it.

Context: Issue puppeteer/puppeteer#12257 (closed, 28 comments): the browser silently disconnected in Docker with no error at all. A maintainer (OrKoN) filed the upstream Chromium bug and gave the workaround, which the reporter confirmed works.