Systemd-docker timout on shutdown

Third Party Help
1

I have followed the following instructions on setting up bitwarden_rs with systemd-docker.

However when rebooting or stopping the service I get the following logs:
Sep 09 14:00:18 bitwarden systemd[1]: Stopping Bitwarden…
Sep 09 14:01:48 bitwarden systemd[1]: bitwarden.service: State ‘stop-sigterm’ timed out. Killing.
Sep 09 14:01:48 bitwarden systemd[1]: bitwarden.service: Killing process 1832 (bitwarden_rs) with signal SIGKILL.
Sep 09 14:01:48 bitwarden systemd[1]: bitwarden.service: Killing process 1832 (bitwarden_rs) with signal SIGKILL.
Sep 09 14:01:48 bitwarden systemd[1]: bitwarden.service: Failed with result ‘timeout’.
Sep 09 14:01:48 bitwarden systemd[1]: Stopped Bitwarden.

This seems incorrect that systemd has to kill the process like this. I know I can probably lower the timeout so it doesn’t take a couple minutes to shutdown the system, but if there is some processes that is not closing down properly I would much rather fix that. I am not sure where the next place to look would be to understand/resolve this issue. Or is this safe ignore?

Bitwarden_RS version 1.16.3
systemd-docker version Version: 0.2.1+dfsg-2
Ubuntu 18.04 x64

Thanks

2

After further research it appears to be related to the following issue:

The current version of Rocket being used does not handle the stop-sigterm signal.