I have several Docker stacks running, including Sablier. When I start everything with docker compose up -d, the stacks that are managed by Sablier remain active even after their configured session duration has passed.
It seems that Sablier only detects and expires these services after I manually visit their URLs - at which point it “discovers” them and correctly terminates the sessions after the specified duration.
Is this the intended behavior, or am I missing a configuration step?
I have several Docker stacks running, including Sablier. When I start everything with docker compose up -d, the stacks that are managed by Sablier remain active even after their configured session duration has passed.
It seems that Sablier only detects and expires these services after I manually visit their URLs - at which point it “discovers” them and correctly terminates the sessions after the specified duration.
Is this the intended behavior, or am I missing a configuration step?