[GH-ISSUE #835] Unexpected handling of SIGTERM #401

Closed
opened 2026-02-26 10:32:23 +03:00 by kerem · 3 comments
Owner

Originally created by @justinlocsei on GitHub (Nov 19, 2025).
Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/835

I noticed today that the handling of SIGTERM appears to have changed between version 7.5.0.1 and 9.1.0.1. For the former version, if I start a container and use docker stop, it receives the signal, shuts down gracefully, and exits with a status of 143. For the latter version, taking the same actions results in the signal being ignored and the container eventually being killed with an exit code of 137.

To reproduce this behavior, you can run the following commands:

docker run --rm -it onlyoffice/documentserver-de:7.5.0.1
docker stop <container> # Exits with 143

docker run --rm -it onlyoffice/documentserver-de:9.1.0.1
docker stop <container> # Exits with 137

It looks like the signal-handling behavior changed back in July, so my guess is that this landed in a version between 7.5.0.1 and 9.1.0.1. Is this change in behavior expected? If so, is there a workaround that would allow the container to gracefully exit, rather than being killed?

Originally created by @justinlocsei on GitHub (Nov 19, 2025). Original GitHub issue: https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/835 I noticed today that the handling of `SIGTERM` appears to have changed between version 7.5.0.1 and 9.1.0.1. For the former version, if I start a container and use `docker stop`, it receives the signal, shuts down gracefully, and exits with a status of 143. For the latter version, taking the same actions results in the signal being ignored and the container eventually being killed with an exit code of 137. To reproduce this behavior, you can run the following commands: ```sh docker run --rm -it onlyoffice/documentserver-de:7.5.0.1 docker stop <container> # Exits with 143 docker run --rm -it onlyoffice/documentserver-de:9.1.0.1 docker stop <container> # Exits with 137 ``` It looks like the signal-handling behavior changed [back in July](https://github.com/ONLYOFFICE/Docker-DocumentServer/pull/753), so my guess is that this landed in a version between 7.5.0.1 and 9.1.0.1. Is this change in behavior expected? If so, is there a workaround that would allow the container to gracefully exit, rather than being killed?
kerem 2026-02-26 10:32:23 +03:00
Author
Owner

@igwyd commented on GitHub (Nov 20, 2025):

Hello @justinlocsei thank you for the report, I can configrm this is bug #78605

<!-- gh-comment-id:3556132822 --> @igwyd commented on GitHub (Nov 20, 2025): Hello @justinlocsei thank you for the report, I can configrm this is bug #78605
Author
Owner

@igwyd commented on GitHub (Dec 1, 2025):

It's fixed at git.onlyoffice.com/ONLYOFFICE/Docker-DocumentServer@d3d6bcf8b4 and will be released in the next release.

<!-- gh-comment-id:3595423272 --> @igwyd commented on GitHub (Dec 1, 2025): It's fixed at https://git.onlyoffice.com/ONLYOFFICE/Docker-DocumentServer/commit/d3d6bcf8b4293bba46dd3cde70df643fffca8f42 and will be released in the next release.
Author
Owner

@Rita-Bubnova commented on GitHub (Dec 3, 2025):

DocumentServer v9.2.0 is released so I close this issue. Feel free to comment or reopen it if you got further questions.

<!-- gh-comment-id:3607413663 --> @Rita-Bubnova commented on GitHub (Dec 3, 2025): DocumentServer v9.2.0 is released so I close this issue. Feel free to comment or reopen it if you got further questions.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Docker-DocumentServer-ONLYOFFICE#401
No description provided.