Closed danteali closed 3 months ago
That's right, the default config is stateful
I'll probably change that in the next release.
I'll investigate your storage initialization issue. Any update since ?
I haven't tried playing with saving states since I logged this. I'm fine using using stateless.
If I get time later I'll try to re-start with save states enabled and let you know.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
Describe the bug When using command
--storage.file="/etc/sablier/my-states.json"
the container won't start and outputs error:The same error occurs whether I try to mount the file to the local filesystem or not (i.e. even if I have mounted a file to the correct path in the container it still says that no file exists).
If I instead try to do it with an environment variable (
- STORAGE_FILE="/etc/sablier/my-states.json"
) the container does start but no file is created.I also note that the docs for this setting state:
So by default (i.e. without specifying this config value) I didn't expect any state to be saved. But when the container is run without using this command arg or the environment variable the docker logs indicate that
/etc/sablier/state.json
is being used to save the state:And the default
/etc/cablier/sablier.yaml
config file inside the container specifies:So it looks like the service is trying to save the state. However nothing seems to be written to this file at all, it remains unchanged when containers are started/stopped.
Context