Polling doesn't stop on receiving SIGTERM in Docker
See original GitHub issueI have been using docker for a while and I have noticed 10 second delay before stopping the container. Now I realized that it is because aiogram doesn’t shutdown when SIGTERM signal was sent. When do docker kill --signal SIGINT, everything looks normal now.
Is it possible to make aiogram to shutdown on SIGTERM as well?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:14 (5 by maintainers)
Top Results From Across the Web
Developers - Polling doesn't stop on receiving SIGTERM in Docker -
Polling doesn't stop on receiving SIGTERM in Docker. ... Now I realized that it is because aiogram doesn't shutdown when SIGTERM signal was...
Read more >Best practices for propagating signals on Docker - Kaggle
When Docker recieves SIGTERM , it forwards the signal to the container and then exits immediately. It does not wait for the container...
Read more >master process running in container doesn't get SIGTERM on ...
As this issue says, it seems like the process running inside the container isn't getting the SIGTERM sent by Docker. I have the...
Read more >child_process didn't receive SIGTERM inside docker container
I try to kill application three different way and none of them works. Application didn't receive SIGTERM no before exit and after manually ......
Read more >Why Your Dockerized Application Isn't Receiving Signals
So if you've ever wondered why your docker stop takes so long – this might be the reason: you didn't listen for SIGTERM...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@kamikazebr yes, I have already deleted the bot after 2days
Solved the problem by setting handlers myself