Open stephannielsen opened 1 year ago
Here is the diff between 5.0.0 and 5.1.0, maybe you can tell from the changes why this occurs:
https://github.com/parse-community/parse-dashboard/compare/5.0.0...5.1.0
I already checked but the changes to the image and CI don't seem like they could cause this.
I noticed in the ci.yml
that platform linux/arm64/v8
is commented because it breaks the build.
But that change was made over 2 years ago. Docker image v5.0.0 was released after that and works fine for me (despite it apparently should not?).
@mtrezza maybe #2534 fixes this?
New Issue Checklist
Issue Description
Starting with release v5.1.0 the published Docker image on Docker Hub no longer has a matching manifest for linux/arm64/v8. When running the Docker image, this message is returned when pulling the image:
With release 5.0.0 there is no problem. Is there a specific reason, why the published image was changed? This prevents us from using the latest version locally (M1 Mac) and in deployments (Linux).
Steps to reproduce
Pull the image on Linux/Mac M1/ARM.
Actual Outcome
no matching manifest for linux/arm64/v8 in the manifest list entries
Expected Outcome
Image can be run on linux/arm without issue as before.
Environment
Starting with v5.1.0 the problem occurs, also with 5.2.0.
Dashboard
> 5.0.0
Server
not relevant
Database
not relevant
Logs
no matching manifest for linux/arm64/v8 in the manifest list entries