INFO SignalAccount - Config file is in use by another instance, waiting…

[shiwusa]

When Signal CLI daemon is running in Docker, executing account related CLI command (like listIdentities) hangs indefinitely at "Config file is in use by another instance, waiting..." after restarting docker container.

Using Docker Volumes did not resolve the issue as well as cleaning .lock files or .local.

Would be grateful for any suggestions.

Environment: Signal CLI version: 0.13.18 (also tested 0.13.17.1)
Platform: Docker (Windows host)

signal-cli --output json --service-environment live --trust-new-identities on-first-use -vv -a +4... listIdentities
2025-09-10T21:09:31.246Z [main] DEBUG org.asamk.signal.util.IOUtils - XDG_RUNTIME_DIR not set, falling back to temp dir
2025-09-10T21:09:31.253Z [main] DEBUG org.asamk.signal.App - Starting signal-cli 0.13.18
2025-09-10T21:09:31.402Z [main] TRACE org.asamk.signal.manager.Manager - Expected exception when checking libsignal-client: Failed to deserialize zkgroup::api::groups::uuid_ciphertext::UuidCiphertext
2025-09-10T21:09:31.402Z [main] DEBUG org.asamk.signal.util.IOUtils - XDG_DATA_HOME not set, falling back to home dir
2025-09-10T21:09:31.425Z [main] TRACE org.asamk.signal.App - Loading account file for +4...
2025-09-10T21:09:31.470Z [main] TRACE o.a.s.manager.storage.SignalAccount - Opening account file
2025-09-10T21:09:31.470Z [main] INFO  o.a.s.manager.storage.SignalAccount - Config file is in use by another instance, waiting…

[ebonit]

if the daemon is running through DBus:
signal-cli --dbus-system listIdentities

see also #1894