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

Dusk dependencies fails to build on MacOS (M1 apple chip) #2992

Closed
lfrichter opened this issue Jun 8, 2021 · 2 comments
Closed

Dusk dependencies fails to build on MacOS (M1 apple chip) #2992

lfrichter opened this issue Jun 8, 2021 · 2 comments

Comments

@lfrichter
Copy link

Description:

When INSTALL_DUSK_DEPS=true, workspace fails on MacOs using M1 apple chip

Expected Behavior:

Is expected to build workspace correctly

Context information:

Output of git rev-parse HEAD

3d57064466e3232cecc6c47ebdf9ca164b8773c3

Output of docker version

Docker version 20.10.6, build 370c289

Output of docker-compose version

docker-compose version 1.29.1, build c34c88b2

System info: Mac, Windows or Linux. Include which disto/version

MacOs Big Sur 11.4 (20F71) - M1 Apple chip

Steps to reproduce the issue:

  1. Change file .env update line INSTALL_DUSK_DEPS=true,
  2. Rebuild using docker-compose build --no-cache workspace
  3. Pop up the error message

Stacktrace & Additional info:

2021-06-08 12:23:56 (3.37 MB/s) - ‘google-chrome-stable_current_amd64.deb’ saved [83335940/83335940]

dpkg: error processing archive google-chrome-stable_current_amd64.deb (--install):
 package architecture (amd64) does not match system (arm64)
Errors were encountered while processing:
 google-chrome-stable_current_amd64.deb
@stale
Copy link

stale bot commented Sep 9, 2021

Hi 👋 this issue has been automatically marked as stale 📌 because it has not had recent activity 😴. It will be closed if no further activity occurs. Thank you for your contributions ❤️.

@stale stale bot added the Stale label Sep 9, 2021
@stale
Copy link

stale bot commented Oct 1, 2021

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.

@stale stale bot closed this as completed Oct 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants