-
-
Notifications
You must be signed in to change notification settings - Fork 784
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 binary in docker image #732
Comments
Wouldn't it be better to signal-cli in a separate container? |
That's what I initially did, sharing the signal socket between the containers. |
Did sharing the socket between the containers not work? What problem did you hit? |
I did manage to share the socket between the containers. The issue is when testing my Signal integration: |
I got it semi-working with the following docker-compose file:
And I had this in
But using volumes to share sockets is quite clumsy. I had permission problems with socket files – I had to chmod the socket file so the healthchecks process would be able to access it. And, after stopping and restarting containers, the signal-cli container complained about the socket file already being there – I had to manually remove it between restarts. I'm inexperienced with docker, there may be proper ways to solve the above issues. As an experimental alternative I added support for connecting to a TCP socket in 73a5cb0. TCP communication between containers is simpler–no volumes, no sokcet files:
And I had this in
|
It seems the signal-cli binary in not included in the docker image.
It is needed for the Signal integration
Would it be possible to make it available ?
Edit: Submitted #733
The text was updated successfully, but these errors were encountered: