-
Notifications
You must be signed in to change notification settings - Fork 138
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
can run this docker image on arm64 #248
Comments
Do you get the same if you run the command directly on the host system and not inside the docker container? |
Yes Host: container: |
That's really strange. Unfortunately, I do not have arm64 hardware at hand, so I cannot directly test it. But I just emulated arm64 on my x86-64 machine with QEMU and that is working fine. I also know of a bunch of other users who run it on a Raspberry Pi 4 (with a 64bit OS). If you have a spare SD card at hand, you could try to install Raspbian (the 64bit version!) and the docker daemon on it and use the |
I'm running into the same problem trying to run this image with docker-compose. Running Libreelec on my Raspberry 4. It has a 64bit kernel with a 32bit userspace. I hope that it's possible to fix this some way, because I really like to use it with my HA integration running on the same system. |
Showing the qrlink with http://192.168.0.10:8080/v1/qrcodelink?device_name=signal-api is working though. On the Libreelec forum they write that I can't use aarch64 docker containers, I need to use arm (32bit) containers. |
@malfino @fr1sty Did you find any solution for this issue? Running into the same issue on my RPi 4 Model B using Raspberry Pi OS, both on bullseye (current OLDSTABLE) and on bookworm (current STABLE). Have tried both signal-cli-rest-api v0.70 and v0.80. This problem first occurred when my previous installation stopped working somewhen between 2023-11-29 and 2023-12-01 when my setup started to get http 422 when trying to fetch messages (without any software update from my side). I suspected a change in the signal APIs server-side and since I hadn't upgraded anything for many months I started to upgrade first this docker image and then my RPi OS. With no success, getting this exception when CURLing cat /proc/cpuinfo | grep Model
uname -m (on both the host OS and inside the signal-cli-rest-api container)
Here is the stacktrace I'm getting (slightly different to the original stacktrace posted above, but most probably because of newer versions):
|
It was a problem with the premade docker image. I installed it manually and then it worked. |
Thanks @malfino, I am trying to build the docker image myself on my aarch64 RPi using these steps:
However the code in the Dockerfile for including signal-cli library for aarch64 architecture seems broken: I changed the line in the Dockerfile to this based on these instructions, i.e. "signalcli" instead of "focal":
But I am still getting this error when trying to build the image on my aarch64 RPi:
@morph027 Is this documentation still up-to-date?
|
When specifying an arch filter
However I would expect all the packages provided by your deb repo. Looking at the Packages specification for binary-arm64 in the signal-cli deb repo, the difference is that the two packages found by apt-cache search above specify I will try to build the docker image by downloading the deb package manually instead, the Dockerfile has already some commented-out lines using a similar workaround:
|
Hm, right, that's weird. It is the proper architecture (compared to any other package like |
|
I can confirm that after doing a clean install of latest RPi OS Desktop (bookworm), the docker image from docker hub works like a charm. If you run into similar problems when running (or building) the docker image on a 64-bit RPi, make sure that both these commands print correct values:
|
As the issue was created a long time ago, I'll close this one now. In case anyone still experiences any issues, please create a new issue. |
The problem
Hi, I installed this docker image through home assistant on my raspberry pi 4 with ubuntu (arm64).
uname -m in the docker container says: aarch64
When I check the /var/log/signal-cli-json-rpc-1/out.log
it says:
Is there an easy way to fix this?
Are you using the latest released version?
Have you read the troubleshooting page?
What type of installation are you running?
Home Assistant Signal Addon
In which mode are you using the docker container?
JSON-RPC Mode
What's the architecture of your host system?
arm64
Additional information
No response
The text was updated successfully, but these errors were encountered: