Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

signal-cli config does not default to /home/.local/share/signal-cli/ so account information does not persist #582

Open
2 tasks done
eric72777 opened this issue Sep 8, 2024 · 1 comment

Comments

@eric72777
Copy link

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 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

@bbernhard
Copy link
Owner

Can't reproduce that issue. Have you maybe set the SIGNAL_CLI_CONFIG_DIR environment variable before (to some other value)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants