Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Published docker image has no matching manifest for linux/arm64/v8 #2501

Open
4 tasks done
stephannielsen opened this issue Sep 20, 2023 · 4 comments · May be fixed by #2534
Open
4 tasks done

Published docker image has no matching manifest for linux/arm64/v8 #2501

stephannielsen opened this issue Sep 20, 2023 · 4 comments · May be fixed by #2534
Labels
type:bug Impaired feature or lacking behavior that is likely assumed

Comments

@stephannielsen
Copy link

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:

no matching manifest for linux/arm64/v8 in the manifest list entries

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

  • Parse Dashboard version: > 5.0.0

Server

  • Parse Server version: not relevant

Database

  • System (MongoDB or Postgres): not relevant

Logs

no matching manifest for linux/arm64/v8 in the manifest list entries
@parse-github-assistant
Copy link

Thanks for opening this issue!

  • 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

@mtrezza
Copy link
Member

mtrezza commented Sep 21, 2023

Here is the diff between 5.0.0 and 5.1.0, maybe you can tell from the changes why this occurs:

5.0.0...5.1.0

@mtrezza mtrezza added the type:bug Impaired feature or lacking behavior that is likely assumed label Sep 21, 2023
@stephannielsen
Copy link
Author

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.

https://github.com/parse-community/parse-dashboard/blob/86c45d870a56c6366df25aa9eada0b8532bbc6a5/.github/workflows/ci.yml#L79C1-L85C46

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?).

@stephannielsen stephannielsen linked a pull request Mar 25, 2024 that will close this issue
Open
3 tasks
@stephannielsen
Copy link
Author

@mtrezza maybe #2534 fixes this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type:bug Impaired feature or lacking behavior that is likely assumed
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Dashboard not building for docker platform arm64/v8 cbaker6/parse-dashboard
2 participants
@stephannielsen @mtrezza