[BUG] Pulling lscr.io/linuxserver/tautulli:latest is failing for amd64

[talz13]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Updating my stack with tautulli, started getting this error as of this week:

tautulli Error context canceled no matching manifest for linux/amd64 in the manifest list entries
The tautulli section of my yaml contains this:
tautulli:
image: lscr.io/linuxserver/tautulli:latest
container_name: tautulli

Expected Behavior

It should pull the amd64 build from the latest tag successfully.

Steps To Reproduce

1. Run Docker on an amd64 system
2. Configure a Docker Compose with the following yaml:
3. tautulli:
   image: lscr.io/linuxserver/tautulli:latest
   container_name: tautulli
4. Pull the compose

Environment

- OS: Synology DSM 7.2.2
- How docker service was installed: Through the Container Manager app

CPU architecture

x86-64

Docker creation

tautulli:
    image: lscr.io/linuxserver/tautulli:latest
    container_name: tautulli

Container logs

n/a

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

[thespad]

Can't see any issue with the latest image

$ docker pull lscr.io/linuxserver/tautulli:latest
latest: Pulling from linuxserver/tautulli
a5e3ea2009e2: Already exists 
e1cde46db0e1: Already exists 
46f2d9bbcff7: Already exists 
f2d94bf0c7ba: Already exists 
0469477658fc: Already exists 
35e63de34f77: Already exists 
681cde493f59: Already exists 
fd555a22c30a: Pull complete 
56212d13c637: Pull complete 
Digest: sha256:f8fa87017ad9252f6135236b040b236efb0e9042fb570a5c0c982aace0ffd478
Status: Downloaded newer image for lscr.io/linuxserver/tautulli:latest
lscr.io/linuxserver/tautulli:latest

What do you get if you run docker pull lscr.io/linuxserver/tautulli:amd64-latest?

[talz13]

Sorry, my issue, it just happened to be the last one on the list. I'm running through my YAML and selectively enabling each image to see which one is ACTUALLY causing the issue.

[talz13]

Aha, it was the readarr image. I see that was deprecated, so I'll just leave it out of my stack from now on.

Closing!