[BUG] "no matching manifest for linux/arm/v8 in the manifest list entries"

[Murffyp]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Not sure if this is a bug,, or something im doing wrong with the command (tried both docker compose and building the image locally... get this error regardless. Im relatively new to docker, but to me it seems either there's an issue with the manifest and the arm64 version isnt there (I'm guessing that's not the issue) or somewhere along the line in determining which image to pull, my architecture is labelled as "linux/arm/v8" instead of "arm64v8" (which my system is... Raspberry Pi 8Gb, 6b bit OS (Rasbian 12 (Bookworm ))).

Expected Behavior

System architecture to be determined correctly and the correct image pulled for docker to use. As mentioned above, I'm guessing somewhere along the line in determining which image to pull, my architecture is labelled as "linux/arm/v8" instead of "arm64v8".

Steps To Reproduce

1. Environment: Raspberry Pi Os (desktop version, but using command line) 64bit Bookwork (Raspbian 12).
   2.,3.,4. Tried many ways to get the image: A) "docker pull linuxserver/snapdrop", "docker pull lscr.io/linuxserver/snapdrop:latest", docker pull linuxserver/snapdrop:version-b8b78cc2, "docker pull linuxserver/snapdrop:version-9c08ff25879b", "docker pull --platform lscr.io/linuxserver/snapdrop/arm64:latest", "docker pull lscr.io/linuxserver/snapdrop/arm64:latest", "docker pull lscr.io/linuxserver/snapdrop:arm64 latest", "docker pull lscr.io/linuxserver/snapdrop:arm64-latest" [[All gave either the aforementioned error, or a syntax error and showed the docker --help output]]. B) Following the build instructions on the docker hub page [[both doing i) gitclone, cd, then build AND ii) pasting all of the commands at once and hitting enter... i) gave me the docker --help output, while ii) started to build until (im guessing) the server (Lscr.io/linuxserver) was involved and the build failed with the aforementioned manifest error. Also on the off chance it MIGHT work, I also tried iii) "docker run --rm --privileged lscr.io/linuxserver/qemu-static --reset" which resulted in an error (multi-line, line breaks signified with "\") "Unable to find image 'lscr.io/linuxserver/qemu-static:latest' locally latest \\ Pulling from linuxserver/qemu-static \\ docker: no matching manifest for linux/arm/v8 in the manifest list entries. \\ See 'docker run --help'.". C) Various alterations to image line in docker-compose.yml (base compose file copied form github page). I didn't save most of the various versions of the docker-compose.yml ifle, but the ones i saved I tried: i) "image: lscr.io/linuxserver/snapdrop:latest", "image: ghcr.io/linuxserver/baseimage-alpine-nginx:arm643.20", "image: linuxserver/snapdrop/arm64v8:latest", and "image: lscr.io/linuxserver/snapdrop:arm64v8-latest" [[not necessarily in that order]]. Oh and at one point in "A)" I was prompted with an error saying I might need to login to be able to download, I did so and received an error about the image not existing in the manifest. Basically out of ideas to try now.

Attached Files:
build commands tested and results.txt
docker-compose file contents and errors.txt
pull commands and results.txt

Environment

- OS:Bookworm 64 bit
- How docker service was installed:
using apt-get for the certificate for curl, curl for the files...etc the official install instructions

CPU architecture

arm64

Docker creation

See files attached above (docker compose files along with output/error for each)

Additionally, logs for the various "pull" commands  tried (outlined above) as well as the "build" commands are provided above.

Container logs

No container logs as unable to pull or build the image.

[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.

[RobertD502]

@Murffyp The README was updated in the latest release to include:
This image is deprecated. We will not offer support for this image and it will not be updated. Consider switching to https://github.com/linuxserver/docker-pairdrop for similar functionality.

With them no longer maintaining an image for snapdrop, there was no linux/amd64 image within the latest tag:

Only solution is to switch over to PairDrop.

[thespad]

When we deprecate an image we intentionally push an empty manifest for the latest tags to prevent people from accidentally pulling an image that is no longer supported, see https://info.linuxserver.io/issues/2024-08-11-deprecation-changes/

That aside, your host is reporting an arch of linux/arm/v8 which means you've got a mixed 32/64bit install and are likely to run into issues across the board because if it, thanks to the frankly stupid decision that Raspbian made to silently upgrade existing users' kernels to 64-bit but leave userspace as 32-bit.