Installation Failed on GMKTEK G3 PLUS

[oscardgrouch82]

Dears. I tried installing the mediastack on a GMKTEK with these specifications: Ubuntu Server OS, X86 linux/amd64 architecture but I am facing the error: "no matching manifest for linux/amd64 in the manifest list entries". I even tried adding the platform=linux/amd64 under each service in the docker compose file but I am still facing the same issue.

PS: docker pull --platform=linux/amd64 traefik:v2.10 is able to sucessfully pull the image

[Todderbod]

I'm having the same exact issue. Did you get it figured out?

[oscardgrouch82]

Nope. Still awaiting the gods

[Todderbod]

I get to were it starts to pull the images and I get no matching manifest for linux/amd64 in the manifest list entries
I have tried to # out some of the programs in the docker-compose file. I'm pretty new to this the old way I could at least launch the stack I was just having trouble setting up my storage. This new way I followed all of the instructions and keep getting this error. Hopefully someone with more knowledge will chime in and point us in the right direction

[oscardgrouch82]

[rightfittech]

I'm running into a similar issue. I'm using Proxmox for the hypervisor with Ubuntu 24.04 LTS as the Docker host. I'm going to walk through each image and see where it's failing.

[rightfittech]

I'm still going through the list but I did find one issue with the images being used. Readarr is failing with the following:

develop: Pulling from linuxserver/readarr
no matching manifest for linux/amd64 in the manifest list entries

It appears that they announced the retirement of the platform on 6/27/2025 and that the work involved in fixing the manifest errors has proven to be more than they want to maintain. They have some options available but it's probably worth pulling from the script for now.

[rightfittech]

I'm new to Github so not sure if this is the correct place to put notes, but I found that comments on lines 47 & 48 of the .env create unnecessary folders in the appdata directory. Basically, when the bash script runs and reads the file, it must not clear the variables and reads the comment as part of the process so that every entry is a new folder "# <-- Update for your folders - Synology Example:"

[oscardgrouch82]

@rightfittech Have You been able to successfully pull the images?

[sjpilot]

To temporarily fix, change the tag on the readarr from develop to 0.4.18-develop
Before:

  readarr:
    image: lscr.io/linuxserver/readarr:develop

After:

readarr:
    image: lscr.io/linuxserver/readarr:0.4.18-develop    

Note: I am new to this repo so whilst lots of containers have started, I haven't tested yet.

[oscardgrouch82]

@rightfittech Thanks old mate. That solved the problem of pulling the images.