🐛 Reap zombie Chromium processes in the exporter container (#12969)

* 🐛 Reap zombie Chromium processes in the exporter container

The exporter runs node as PID 1 with no init process. Chromium helper
processes orphaned when Playwright closes a browser are re-parented to
node, which never reaps them, so every browser-based export left
defunct chrome-headless processes behind.

Enable init for the exporter service so Docker's built-in init runs as
PID 1, reaps the orphans and forwards signals to node.

Closes #10339

Signed-off-by: Rayen Khammar <khammarrayen4@gmail.com>

* 🐛 Move zombie reaping fix into the exporter image

Install tini and run it as the image entrypoint with -s, so orphaned
Chromium helpers are reaped in every deployment, including Kubernetes.
-s keeps tini working without a warning when it runs under docker-init
(init: true). Drop the compose init: true change to keep one mechanism.

Signed-off-by: Rayen Khammar <khammarrayen4@gmail.com>

---------

Signed-off-by: Rayen Khammar <khammarrayen4@gmail.com>
This commit is contained in:
Rayen Khammar 2026-11-17 11:41:43 +01:00 committed by Andrey Antukh
parent 38a9878981
commit fa1249c1a5

View File

@ -17,6 +17,7 @@ RUN set -ex; \
locales \
ca-certificates \
gzip \
tini \
; \
apt-get clean; \
rm -rf /var/lib/apt/lists/*; \
@ -126,4 +127,5 @@ RUN ./setup && chown -R penpot:penpot /opt/penpot/exporter
USER penpot:penpot
ENTRYPOINT ["/usr/bin/tini", "-s", "--"]
CMD ["node", "app.js"]