Closed refrain closed 2 years ago
I think I figured out the issue... my raspberry pi is aarch64 and i need to specify the arm64 digest when pulling:
docker pull fetzu/teslamate@sha256:4f5bc335da8fa21d5f92f6aa8301165fcb401b09fe10303f8857a17fb90a9f94
Sorry for the late reply.
I've looked into it, and I can't tell why your RasPi was not recognizing it should pull the arm64 image. AFAIK an arm64 build = aarch64 build. Glad you could find the solution.
I updated the rpi release to Bullseye (from Buster) since I posted, and the error message is slightly different:
ERROR: for abrp no matching manifest for linux/arm/v7 in the manifest list entries
However, my previous solution is working and I am getting the current SoC from ABRP live.
@refrain: I added a linux/arm/v7 build to the workflow and it seems like everything has built fine and was pushed to DockerHub. It might work out of the box if you pull the latest image.
Please feel free to let me know if it doesn't.
@fetzu: just wanted to report back that this is now working without the need to specify the digest on my rasp pi 4. Didn't get around to testing it till now... Thanks for fixing it though, as it will definitely help when the image gets updated and users won't need to look up the new digest every time.
@refrain You are welcome, I glad it worked on the first try :)
Error trying to pull your docker image: fetzu/teslamate-abrp:latest
ERROR: for ABRP no matching manifest for unknown in the manifest list entries ERROR: no matching manifest for unknown in the manifest list entries