No v4.0.1 image for raspberry pi when only 32 bit docker installed

[ajmoerdijk-bot]

Installed Teslamate last november on my Raspberry Pi and was happily enjoying it (v2.2.0) untill I returned from holidays and discovered that it had stopped working since 12-6.
Underlying problem is apparently solved with v4.0.1, but looks like there is no image for that version yet for Pi as I could get up to v3.1.0 by using docker compose pull, but for v4.0.0 and v4.0.1 I got "no matching manifest for linux/arm/v8 in the manifest list entries", indicating there is no image for the arm architecture (yet).

Can anyone help to get an image for us Pi users ?
Thanks
AJ.

[brianmay]

The platform is called "linux/arm64" not "linux/arm/v8". "linux/arm/v8" is not published, but "linux/arm64" is.

My understanding is this is because you have an older install that adapted unofficial conventions. And you will need to override the platform. LLM says (untested!):

bashdocker pull --platform linux/arm64 teslamate/teslamate:v4.0.1

Or in your docker-compose.yml:

yamlservices:
  teslamate:
    image: teslamate/teslamate:v4.0.1
    platform: linux/arm64

[ajmoerdijk-bot]

steps 2-5 resulted in this message from docker compose up:
! teslamate The requested image's platform (linux/arm64) does not match the detected host platform (linux/arm/v8) and no specific platform was requested 0.
Followed by (a lot of other messages from grafana and progres): teslamate-1 exited with code 159 (restarting)

[ajmoerdijk-bot]

@cwanja, you have the same compose.yml that @JakobLichterfeld refers to ( https://docs.teslamate.org/docs/installation/docker/ )?

[cwanja]

@ajmoerdijk-bot can confirm that is the case. My Pi was reporting as arm7 which made me then think #5304 was relevant to me. But @JakobLichterfeld said I should have no issues grabbing a 64bit Raspberry Pi OS for my 3b+ and install. And that was exactly the case. Backed up my files, database and re-installed the OS. Reinstalled Docker. Pull immediately worked. Restored the DB and all my data was there from the backup. Did not even have to log back in, due to the tokens being in the database and the encryption key being the same.

[brianmay]

I am unclear when/why you would see "linux/arm/v8". One reference said it is the same as aarch64. Suspect this is not correct in this particular case. This does seem more like a 64 bit kernel but 32 bit user space.

[ajmoerdijk-bot]

Guess you are correct @brianmay.
Made a new 64 bit image, re-setup my Pi and got Teslamate up and running again with the standard compose.yml on version 4.0.1 and managed to restore the data collected.
Pity it took a few days, but learned a lot thanks also to you all.

[Bzzz]

Additional info for everyone else with the armv8 error message while the rest of the RPi (4) system screams 64bit: Well, check your docker installation. I had :armhf docker packages, for whatever reason, and therefore it always pulled in 32bit images (and if explicitly told to fetch 64bit, they wouldn't run for a variety of reasons).

uname -a
Linux raspberrypi4 6.12.93+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.93-1+rpt1 (2026-06-12) aarch64 GNU/Linux

dpkg -l | grep docker
ii  docker-buildx-plugin:armhf             0.31.1-1~raspbian.12~bookworm            armhf        Docker Buildx plugin extends build capabilities with BuildKit.
ii  docker-ce:armhf                        5:28.5.2-1~raspbian.12~bookworm          armhf        Docker: the open-source application container engine
ii  docker-ce-cli:armhf                    5:28.5.2-1~raspbian.12~bookworm          armhf        Docker CLI: the open-source application container engine
ii  docker-ce-rootless-extras:armhf        5:28.5.2-1~raspbian.12~bookworm          armhf        Rootless support for Docker.
ii  docker-compose-plugin:armhf            5.0.2-1~raspbian.12~bookworm             armhf        Docker Compose (V2) plugin for the Docker CLI.

Since 32 and 64 bit postgre data structure seems deeply incompatible: Back up your database (well, always back up your stuff, duh!), curl and execute the installer from get.docker.com. Then remove the old database, init a new one, and reseed that backup. Took roughly 10 minutes in my case (~1.8GB dump), then all docker stuff was able to restart - and teslamate 4.0.1 is now running. Okay, I lost about two weeks of stats since the old install wasn't pulling in data since June 12th, but that's what it is, that's why I looked into the thing in the first place. Glad I caught it that early, there's sometimes months that I do not check anything...

I'll probably look into a teslamate monitoring solution next, to avoid that issue in the future :)

[JakobLichterfeld]

Well, check your docker installation.

Nice shootout! I had this idea beforehand but didn't speak out loud.
Makes total sense. Not to have a 32bit Docker but that the issue is caused by misconfigured/mis installation of Docker.