can run this docker image on arm64 about signal-addon

[haberda]

Hello, from the log Possible cause: can't load AARCH64 .so on a ARM platform it looks like you are not running ARM64. For the record, I run this just fine on a Pi4 ARM64 on HASSOS. uname -m in the console should print out what architecture you are running.

However, if there is some underlying issue, the upstream container is where the problem would lie. I simply take the upstream and change some environment variables to work with Home Assistant. It also might be worth just running the upstream directly on Docker rather than the add-on, since you are running Ubuntu anyway.

[haberda]

One other thing, I don't think Native mode works for ARM64. You have to run the normal mode, or maybe json-rpc. From the log it looks like you're trying to run native.

[malfino]

Thank you for your reply. I guess that I'm also on arm64. If I ran uname -m in the docker container, it says

signal-api@1315902c-signal-messenger:/var/log/signal-cli-json-rpc-1$ uname -m
aarch64

The settings in homeassistant sa json-rpc.

I don't hink it is related to running it in normal mode.

OpenJDK Server VM warning: You have loaded library /tmp/sqlite-3.36.0.3-1495367d-8e7d-4b3e-954e-7211a4236025-libsqlitejdbc.so which might have disabled stack guard. The VM will try to fix the stack guard now.
It's highly recommended that you fix the library with 'execstack -c ', or link it with '-z noexecstack'.
Failed to load native library:sqlite-3.36.0.3-1495367d-8e7d-4b3e-954e-7211a4236025-libsqlitejdbc.so. osinfo: Linux/aarch64
java.lang.UnsatisfiedLinkError: /tmp/sqlite-3.36.0.3-1495367d-8e7d-4b3e-954e-7211a4236025-libsqlitejdbc.so: /tmp/sqlite-3.36.0.3-1495367d-8e7d-4b3e-954e-7211a4236025-libsqlitejdbc.so: wrong ELF class: ELFCLASS64 (Possible cause: can't load AARCH64 .so on a ARM platform)

The libsqlitejdcbc.so seems to be the problem, don't you think?

But you are right, I will file this ticket on upstream...

[haberda]

I'd suggest trying uname -m on the host, rather than in the container.

Regardless, see if you can run the upstream container directly in docker. If it works fine, then maybe I can do something on my end. If not then it's an upstream issue.

[malfino]

I installed an upstream docker image directly in docker and it works fine. It's a weird bug. But for now, I'm happy, that I can use it again.

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!