Describe the bug
I've observed that when I create a new container in a group while Sabilier is running, there is a line that says sablier/sablier.go:44 set groups old=... new=... as expected. However, sabilier does not stop them after the session expiration. If I restart sabilier, there is a line says stopped unregistered instance instance=... reason="instance is enabled but not started by Sablier" which means the newly container is being detected but not registered with Sabiler.
Context
- Sablier version: 1.11.1
- Provider: 29.3.0
- Reverse proxy: traefik v3.6.10
- Sablier running inside a container? Yes
Expected behavior
I am expecting that Sabiler will automatically register newly created containers and manage them accordingly.
Additional context
Thank you for Sabiler.
Describe the bug
I've observed that when I create a new container in a group while Sabilier is running, there is a line that says
sablier/sablier.go:44 set groups old=... new=...as expected. However, sabilier does not stop them after the session expiration. If I restart sabilier, there is a line saysstopped unregistered instance instance=... reason="instance is enabled but not started by Sablier"which means the newly container is being detected but not registered with Sabiler.Context
Expected behavior
I am expecting that Sabiler will automatically register newly created containers and manage them accordingly.
Additional context
Thank you for Sabiler.