[BUG] arch issues in manifest

[dmnc-net]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I was updating the Smokeping container on RPi4 with Raspbian Bookworm, after some time of not using it, and I ran into a problem. Regarding the Docker hub page, I should use the tag latest or arm64v8-latest. But pulling generates errors like no matching manifest for linux/arm64v8 in the manifest list entrie or no matching manifest for linux/arm/v8 in the manifest list entries.

When I tried this command, I found out that there is (except amd64) just arm64 ... nothing with v8, etc:

$ docker manifest inspect linuxserver/smokeping:latest

For me, the solution was this command (which I can't achieve by other tools like Portainer):

$ docker pull --platform linux/arm64 linuxserver/smokeping:latest

I believe that the manifest should be adjusted.

Expected Behavior

using docker pull linuxserver/smokeping:latest without any error

Steps To Reproduce

1. run docker pull linuxserver/smokeping:latest
2. see error

Environment

- OS: Raspbian / Raspberry Pi OS - 11 / Bookwork
- How docker service was installed: apt
- Docker version 28.0.0, build f9ced58

CPU architecture

arm64

Docker creation

`docker pull linuxserver/smokeping:latest`

Container logs

latest: Pulling from linuxserver/smokeping
no matching manifest for linux/arm/v8 in the manifest list entries

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[j0nnymoe]

This happens because you've got a 32bit OS installed on 64bit hardware, common issue when using Raspberry Pi OS.
It's a 32bit OS with a 64bit Userland.

[j0nnymoe]

https://www.linuxserver.io/blog/a-farewell-to-arm-hf
This explains a bit about the error you're getting (plus gives some commands to confirm it)