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 default to having the signal-cli config default to /home/.local/share/signal-cli/ so if the user sets up the system per the documentation, the signal account registration information won't persist after a docker compose down.
Temporary Fix for Users
To temporarily fix this, I explicitly added the env variable - SIGNAL_CLI_CONFIG_DIR=/home/.local/share/signal-cli/ and it works fine. However, this isn't the fix for the bug since the container should default to this location per the documentation.
Are you using the latest released version?
Yes
Have you read the troubleshooting page?
Yes
What type of installation are you running?
signal-cli-rest-api Docker Container
In which mode are you using the docker container?
JSON-RPC Mode
What's the architecture of your host system?
x86-64
Additional information
No response
The text was updated successfully, but these errors were encountered:
The problem
The container does not default to having the signal-cli config default to
/home/.local/share/signal-cli/
so if the user sets up the system per the documentation, the signal account registration information won't persist after adocker compose down
.Temporary Fix for Users
To temporarily fix this, I explicitly added the env variable
- SIGNAL_CLI_CONFIG_DIR=/home/.local/share/signal-cli/
and it works fine. However, this isn't the fix for the bug since the container should default to this location per the documentation.Are you using the latest released version?
Have you read the troubleshooting page?
What type of installation are you running?
signal-cli-rest-api Docker Container
In which mode are you using the docker container?
JSON-RPC Mode
What's the architecture of your host system?
x86-64
Additional information
No response
The text was updated successfully, but these errors were encountered: