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.

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

Add arm64 support #2040

Open
4 tasks done
lzzy12 opened this issue Feb 13, 2022 · 6 comments
Open
4 tasks done

Add arm64 support #2040

lzzy12 opened this issue Feb 13, 2022 · 6 comments
Labels
type:feature New feature or improvement of existing feature

Comments

@lzzy12
Copy link

lzzy12 commented Feb 13, 2022

New Issue Checklist

Issue Description

I am unable to run this on a 4 cores arm64 ubuntu server (pulled from dockerhub). It throws exec format error. I assume this is because there is no arm images available on dockerhub? Is there any chance, this could change?

Steps to reproduce

Run the commands to start the app in a docker container being pulled from dockerhub:
docker run -d -p 4040:4040 parseplatform/parse-dashboard --dev --appId $APP_ID --masterKey $MASTER_KEY --serverURL $SERVER_URL

Actual Outcome

exec user process caused: exec format error

Expected Outcome

To run like it would on a normal x86-64 architecture cpu

Environment

ARM64 Ubuntu 20
4 cores
24GB RAM
30GB HDD

Dashboard

  • Parse Dashboard version: latest tag on DockerHub
  • Browser (Safari, Chrome, Firefox, Edge, etc.): Chrome
  • Browser version: 98.0

Server
Not relevant

Database

  • System (MongoDB or Postgres): MongoDB
  • Database version: 4.0
  • Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): local

Logs

standard_init_linux.go:228: exec user process caused: exec format error

@parse-github-assistant
Copy link

parse-github-assistant bot commented Feb 13, 2022

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 mtrezza added the type:feature New feature or improvement of existing feature label Feb 13, 2022
@mtrezza
Copy link
Member

mtrezza commented Feb 13, 2022

Docker images for other platforms presumably failed to build so they have been removed in 190258b.

The error log is unavailable but if you want to open a PR that includes that architecture (or try to build it locally) you'd see the exact error - if it still exists - and we can look into how to go about it.

@hajjD
Copy link

hajjD commented Mar 9, 2022

Just to quickly chime in, you get a similar (but notably different) error message when running the dashboard on Macs with the M1 chip (ARM):

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

@simpros
Copy link

simpros commented Mar 18, 2022

Any Plans on adding support for this growing platform?

@JeffGuKang
Copy link
Contributor

JeffGuKang commented Oct 25, 2022

AWS Graviton (t4g) has error with parse dashboard docker image.

standard_init_linux.go:228: exec user process caused: exec format error"

This answer looks having same situation.

This can happen if you're trying to run an x86 built image on an arm64/aarch64 machine.
You'll need to rebuild the image using the corresponding architecture

link

@mtrezza
Copy link
Member

mtrezza commented Oct 25, 2022

That's interesting, I tried to reproduce this, but Parse Dashboard 5.0.0-beta.1 seems to run fine on t4g.nano with Node 16. If the dashboard itself runs fine, maybe we only need to add the arm docker image build.

I've opened #2334 so we can see which archs fail. The issue seems to be related to puppeteer/puppeteer#7740. There are workarounds described which we could adopt until the issue is fixed, but from reading the thread it seems that any change in the puppeteer version would require a change in the fix. Maybe someone can investigate that more and we can merge a fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature New feature or improvement of existing feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants