Closed orangepeelbeef closed 12 months ago
Yeah, sorry about that. Something changed in signal-cli
. Unfortunately I don't have time at the moment to look into it. Maybe delete the named volume and use the old version.
@orangepeelbeef did you try this? I'm also running into this issue.
@dadevel I took your Dockerfile, and changed from bullseye to bookworm, and built it and things worked afterwards. So I think this is a fairly easy fix.
Oh thanks. I'll push the fix tonight.
Glad you got it working, I ended up switching over to https://github.com/bbernhard/signal-cli-rest-api
On Tue, Sep 19, 2023, 1:13 AM Daniel @.***> wrote:
Oh thanks. I'll push the fix tonight.
— Reply to this email directly, view it on GitHub https://github.com/dadevel/alertmanager-signal-receiver/issues/20#issuecomment-1725032246, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA7ZA6L7GKFGB7YPE4PVNDX3FHZ7ANCNFSM6AAAAAA4VWONFI . You are receiving this because you were mentioned.Message ID: @.***>
I pushed the fixed image. Thanks to @micah again for the tip with Debian Bookworm.
I had my signal receiver container auto-updating with watchtower, and my container is now busted.
serverrequest handler failed: signal-cli: command execution failed: WARN Manager - Failed to call libsignal-client: /tmp/14960838443535371721libsignal_jni.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /tmp/14960838443535371721libsignal_jni.so) Missing required native library dependency: libsignal-client : exit status 1
trying to downgrade back to 1.4.0 tells me my config file is a newer version and no longer compatible. :(