You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The container does not stop after receiving the stop-signal.
For most people this may not be so noticeable because after a 10 second timeout docker will just kill the container. But Im using a timeout of 240 seconds and so it takes multiple minutes for this container to be finally hard-killed by docker.
To reproduce
docker stop -t=240 eufy-ws
Screenshots & Logfiles
The logfiles doesnt show anything about the shutdown process
Additional context
No response
The text was updated successfully, but these errors were encountered:
Updated dependency eufy-security-client to 2.4.3
Updated dependency fs-extra to 11.1.1
Updated dependency ws to 8.13.0
Updated dev dependencies
Updated docs
Version
1.3.4
Node version
16.19.1
Operating System type
Linux
Operating system version
Ubuntu 22.10
Describe the bug
The container does not stop after receiving the stop-signal.
For most people this may not be so noticeable because after a 10 second timeout docker will just kill the container. But Im using a timeout of 240 seconds and so it takes multiple minutes for this container to be finally hard-killed by docker.
To reproduce
docker stop -t=240 eufy-ws
Screenshots & Logfiles
The logfiles doesnt show anything about the shutdown process
Additional context
No response
The text was updated successfully, but these errors were encountered: