rootless feedback

[poggenpower]

I tested with bbernhard/signal-cli-rest-api:0.100-rootless finally it worked as expected even running all the stuff in Kubernetes, but while troubleshooting I found out, this it is not possible to add -v to the signal-cli command, which gives useful logs if doing silly things.

e.g.:

2026-06-18T23:40:06.561Z [Thread-21] INFO  LibSignalService - [LibSignalChatConnection]: [normal:1795803621] connection unexpectedly closed
org.signal.libsignal.net.ConnectedElsewhereException: the server explicitly disconnected us because we connected elsewhere with the same credentials

I am unsure if it is a rootless thing or not, but I have not found a way to set -v except overwriting the entrypoint and exec into the container and run signal-cli manually

[bbernhard]

In which mode you want to add -v and how does your debugging workflow look like?

I usually use -v either with the normal or the native mode (the json-rpc mode is imho a bit more inconvenient to debug). In order to get the actual signal-cli command that's executed in the background, I enable the debug mode and then connect inside the container to run the command directly there (with -v appended, if necessary).