Incomplete container launch after adding PUID/PGID. Stuck at "Setting ownership ..."

Describe the bug

I have a working stack with many proxy entrys, and SSL certs, and want to run as my user/group.

Nginx Proxy Manager Version

2.12.3

To Reproduce
Steps to reproduce the behavior:

1. docker compose up -d

Expected behavior

Full container start-up ending (maybe) in Completed SSL cert renew process

Operating System

Debian 12

Additional context

Logging:

db-1  | [i] pre-init.d - processing /scripts/pre-init.d/01_secret-init.sh
db-1  | [i] mysqld not found, creating....
db-1  | [i] MySQL directory already present, skipping creation
db-1  | 2025-05-06 15:38:43 0 [Note] Starting MariaDB 10.11.5-MariaDB source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 1
db-1  | 2025-05-06 15:38:43 0 [Note] Plugin 'InnoDB' is disabled.
db-1  | 2025-05-06 15:38:43 0 [Note] Plugin 'FEEDBACK' is disabled.
db-1  | 2025-05-06 15:38:43 0 [Note] Server socket created on IP: '0.0.0.0'.
db-1  | 2025-05-06 15:38:43 0 [Note] Server socket created on IP: '::'.
db-1  | 2025-05-06 15:38:43 0 [Warning] 'user' entry '@9eee03f51119' ignored in --skip-name-resolve mode.
db-1  | 2025-05-06 15:38:43 0 [Warning] 'proxies_priv' entry '@% root@9eee03f51119' ignored in --skip-name-resolve mode.
db-1  | 2025-05-06 15:38:43 0 [Note] /usr/bin/mysqld: ready for connections.
db-1  | Version: '10.11.5-MariaDB'  socket: '/run/mysqld/mysqld.sock'  port: 3306  Alpine Linux
app-1  | ❯ Configuring npm user ...
app-1  | ❯ Configuring npm group ...
app-1  | ❯ Checking paths ...
app-1  | ❯ Setting ownership ...

Never proceeds from there.

Start by running docker compose up -d on Debian 12 with the reported PUID/PGID settings and inspect the app container logs around Setting ownership .... No source file or test is named in the report, so trace the container startup entry point responsible for that message. Done means the app proceeds past ownership setup and completes startup, including the expected SSL renewal process.