I’m seeing a repeatable console disconnect in a TurnKey LXC container on Proxmox when inithooks is configured via dpkg --configure -a.

Environment:
Virtualization: lxc
OS: Debian GNU/Linux 13 (trixie)
Kernel: Linux 7.0.14-3-pve
TurnKey app: turnkey-nginx-php-fastcgi-18.0
inithooks version: 2.3.4
turnkey-version: 1.1.3
Hostname: [REDACTED]
CT private IP: [REDACTED]
Client IP: [REDACTED]

When running dpkg --configure -a, the Proxmox CT console disconnects/resets. SSH remains usable, but the interactive Proxmox console session is dropped because the container getty is restarted during package configuration.

Relevant package state before completing configuration:

Package: inithooks
Status: install ok half-configured
Version: 2.3.4

/var/lib/dpkg/info/inithooks.postinst
23 else
24     # getty1 should already be running if inithooks wasn't, but let's
25     # make sure
26     systemctl restart getty@tty1.service container-getty@1.service 2>/dev/null || true
27 fi

Jul 31 18:09:14 [HOST] systemd[1]: Reload requested from client PID [PID] ('systemctl') (unit container-getty@1.service)...
Jul 31 18:09:14 [HOST] systemd[1]: Stopping container-getty@1.service - Container Getty on /dev/tty1...
Jul 31 18:09:14 [HOST] systemd[1]: Stopped container-getty@1.service - Container Getty on /dev/tty1.
Jul 31 18:09:14 [HOST] systemd[1]: Started container-getty@1.service - Container Getty on /dev/tty1.

Jul 31 18:21:00 [HOST] systemd[1]: Reload requested from client PID [PID] ('systemctl') (unit container-getty@1.service)...
Jul 31 18:21:00 [HOST] systemd[1]: Stopping container-getty@1.service - Container Getty on /dev/tty1...
Jul 31 18:21:00 [HOST] systemd[1]: Stopped container-getty@1.service - Container Getty on /dev/tty1.
Jul 31 18:21:00 [HOST] systemd[1]: Started container-getty@1.service - Container Getty on /dev/tty1.

RUN_FIRSTBOOT=false
REDIRECT_OUTPUT=false
SUDOADMIN=false

Is inithooks.postinst expected to restart container-getty@1.service during configure/upgrade on LXC containers when inithooks.service was not active? If this is intentional, is the expected side effect that active Proxmox CT console sessions may be disconnected during dpkg --configure -a or package upgrades?