Impossible to install with docker for mac M1 (linux/arm64/v8)

[mohamedkahoul]

When i try to install cypress from cypress/base:14.15.0 docker image it fails with this message

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

This is the stack trace

Building cypress
Step 1/3 : FROM cypress/base:14.15.0
 ---> 0d8a5b3e7f85
Step 2/3 : RUN npm install --save-dev cypress
 ---> Using cache
 ---> 224f8f3b8c6c
Step 3/3 : RUN $(npm bin)/cypress verify
 ---> [Warning] The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
 ---> Running in 16fc1437571e
[16:04:06]  Verifying Cypress can run /root/.cache/Cypress/6.2.1/Cypress [started]
[16:04:14]  Verifying Cypress can run /root/.cache/Cypress/6.2.1/Cypress [failed]
[16:04:14] → Cypress failed to start.

This is usually caused by a missing library or dependency.

The error below should indicate which dependency is missing.

https://on.cypress.io/required-dependencies

If you are using Docker, we provide containers with all required dependencies installed.

----------

qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
[39:0112/160410.198597:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[39:0112/160410.230391:ERROR:file_path_watcher_linux.cc(315)] inotify_init() failed: Function not implemented (38)
[39:0112/160410.280168:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 1 time(s)
[39:0112/160410.289304:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 2 time(s)
[39:0112/160410.290874:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 3 time(s)
[39:0112/160410.293599:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 4 time(s)
[39:0112/160410.295657:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 5 time(s)
[39:0112/160410.297105:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 6 time(s)
[39:0112/160410.300593:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 7 time(s)
[39:0112/160410.338984:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 8 time(s)
[39:0112/160410.341489:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 9 time(s)
[39:0112/160410.341626:FATAL:gpu_data_manager_impl_private.cc(445)] GPU process isn't usable. Goodbye.
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
[69:0112/160414.318708:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[69:0112/160414.354824:ERROR:file_path_watcher_linux.cc(315)] inotify_init() failed: Function not implemented (38)
[69:0112/160414.404974:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 1 time(s)
[69:0112/160414.411964:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 2 time(s)
[69:0112/160414.413620:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 3 time(s)
[69:0112/160414.416784:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 4 time(s)
[69:0112/160414.469540:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 5 time(s)
[69:0112/160414.489171:WARNING:gpu_process_host.cc(1267)] The GPU process has crashed 6 time(s)
[69:0112/160414.489267:FATAL:gpu_data_manager_impl_private.cc(445)] GPU process isn't usable. Goodbye.
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped


----------

Platform: linux (Debian - 10.6)
Cypress Version: 6.2.1
Cypress failed to start.

This is usually caused by a missing library or dependency.

The error below should indicate which dependency is missing.

https://on.cypress.io/required-dependencies

If you are using Docker, we provide containers with all required dependencies installed.

----------

Platform: linux (Debian - 10.6)
Cypress Version: 6.2.1
ERROR: Service 'cypress' failed to build : The command '/bin/sh -c $(npm bin)/cypress verify' returned a non-zero code: 1

Download method

• npm
• yarn
• Direct download
• Docker image

Operating System

• Linux
• Mac M1 version
• Windows

Other

• I'm installing latest Cypress version
• I'm behind a proxy
• This only occurs in CI

Can you help me please?

[jennifer-shehane]

I'm going to move this issue over to our docker images repo, because I think this is an issue with our docker images and not our actual Cypress product.

[jca41]

Any news on this?

[mohamedkahoul]

Any news on this?

No 😥

[seenickcode]

@jennifer-shehane I feel it may be a good idea to bump this issue up in priority or at least move it over as you mentioned. I'm also getting this on a brand new MacBook Pro 13 with M1 chip. I can run cypress fine on it, just not via the Dockerfile example provided at https://hub.docker.com/r/cypress/base/

[seenickcode]

@bahmutov any update re moving and/or looking in this btw? #431 (comment)

[tarekziade]

I was able to create a custom Docker image that builds cypress on that arch, but there's one problem

Cypress hardcodes the build dir name here https://github.com/cypress-io/cypress/blob/master/scripts/binary/meta.js#L40
On arm64, it's linux-arm64-unpacked , so the process breaks.

If I change that line, everything works fine. So I don't know if I missed something, or if we need to adapt that meta.js file for arm64.

[mayteio]

If I change that line

@tarekziade do I just need to change that line in node_modules?

[jamland]

same issue 😨

[tarekziade]

If I change that line

@tarekziade do I just need to change that line in node_modules?

I've just changed it in the meta.js file.

[mayteio]

@tarekziade can you please be more specific? Do I need to clone the repository, change the file, build the binary? Or just change it in node_modules?

[pkalisiewicz]

hey all, is there any update for this thread?
is there anything we can do to get it sorted out?

[jennifer-shehane]

Wanted to link to our blog post concerning running Cypress on M1 https://cypress.io/blog/2021/01/20/running-cypress-on-the-apple-m1-silicon-arm-architecture-using-rosetta-2/

[jennifer-shehane]

We're open to a pull request to update the build dir name in the cypress repo as mentioned in #431 (comment)

[guilhermestorck]

I created this PR with the changes mentioned on the comment above. @tarekziade, could you please review?

cypress-io/cypress#16530

[obedparla]

For anyone landing here, the PR that @guilhermestorck opened was closed: cypress-io/cypress#16530 (comment).

So a PR is still needed.

[marcoemrich]

I just want to confirm, that we have the same issue we tried the 7.6.0 included Docker image and got this error

[FAILED] Cypress failed to start.
[FAILED] 
[FAILED] This is usually caused by a missing library or dependency.
[FAILED] 
[FAILED] The error below should indicate which dependency is missing.
[FAILED] 
[FAILED] https://on.cypress.io/required-dependencies
[FAILED] 
[FAILED] If you are using Docker, we provide containers with all required dependencies installed.
[FAILED] 
[FAILED] ----------
[FAILED] 
[FAILED] qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
[FAILED] qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
[FAILED] 
[FAILED] 
[FAILED] #
[FAILED] # Fatal error in , line 0
[FAILED] # ignored
[FAILED] #
[FAILED] #
[FAILED] #
[FAILED] #FailureMessage Object: 0x4009bb9c60
[FAILED] qemu: uncaught target signal 4 (Illegal instruction) - core dumped
[FAILED] 
[FAILED] ----------
[FAILED] 
[FAILED] Platform: linux (Debian - 10.10)
[FAILED] Cypress Version: 7.6.0
Cypress failed to start.
This is usually caused by a missing library or dependency.
The error below should indicate which dependency is missing.
https://on.cypress.io/required-dependencies
If you are using Docker, we provide containers with all required dependencies installed.
----------
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
#
# Fatal error in , line 0
# ignored
#
#
#
#FailureMessage Object: 0x4009bb9c60
qemu: uncaught target signal 4 (Illegal instruction) - core dumped
----------

[marcoemrich]

Cypress without Docker works fine on M1

[gerb-ster]

I can confirm this issue as well, would be nice to get it fixed. If I understand correctly this is nothing more then adding a flag to the compiler options somewhere within this image?

[shayaulman]

Does anyone know if this issue is being addressed?

[obedparla]

I can confirm this issue as well, would be nice to get it fixed. If I understand correctly this is nothing more then adding a flag to the compiler options somewhere within this image?

I think the main problem is that their CI (Travis CI) doesn't support M1 yet.

[ollyjshaw]

I'm also facing this issue with Cypress on an M1 via Docker.

[dannyvassallo]

Any progress on this?

[corysimmons]

"Cypress Docker Images don't work on Macs released within the last year."

A lot of devs use Macs... M1's were released in Nov 2020. This issue was opened a couple months later.

It has now been almost a year.

Please fix this.

@chrisbreiding @flotwig @bahmutov

[obedparla]

I can confirm this issue as well, would be nice to get it fixed. If I understand correctly this is nothing more then adding a flag to the compiler options somewhere within this image?

I think the main problem is that their CI (Travis CI) doesn't support M1 yet.

1. this is an open source project. You're welcome to contribute and open a PR to fix it.
2. if you follow this thread you'll see they hadn't fixed it (at that time) due to Travis not offering that build.
3. please be respectful. I'm sure the Cypress team is aware of this issue.

[morenocarullo]

I'm trying to put together a solution for this.
However, it looks like we need to get back one step: the Chrome and Edge binaries included in the Docker images are released only for the amd64 architecture. I'm currently investigating a firefox / chromium build or any other way to have a simple-to-use included image able to run multi-arch.

[LuisMlopez]

Same issue here!!! Any progress???

[ElMenax]

Hello,
Thanks for the image, now Cypress visual tests are working again ⭐
As someone mentioned above, I have now a difference in generated snapshots between the official Cypress image and the cypress-m1 one. In my situation, the font looks slightly different (it seems more bold), see screenshot:

I checked with which Browser tests were run on, and one is Electron 93 (cypress official image, left part of the image) and the cypress m1 is using Electron 94 (right part of the image). Tho I do not think this could cause the difference.

Do you have any ideas or hints of what could be the root cause of this slight difference? @webnexusmobile you mentioned Please note: I didn't add the extra fonts so I wonder if it could be related 🤔

[tisba]

jFYI: Looks like Chrome is finally going to be running fine on aarch64 with 16kb page size (which is required for running on Apple Silicon/M1 in Docker on macOS): https://chromium-review.googlesource.com/c/chromium/src/+/3545665

[patrickathompson]

Anyone try to build a linux/amd64 cypress docker container on an Apple M1 host and been successful? All the solutions above are using arm64 platform within the docker container itself and building it on an Apple M1. A more common scenario would be developing an application on a M1 machine and running it in production under amd64. Wouldn't it make more sense for containers to be built and ran with amd64 arch locally to ensure same environment? This is the route I was trying to take, but getting the same error.

[desprit]

@ElMenax

I have now a difference in generated snapshots between the official Cypress image and the cypress-m1 one

Have you found a solution? I'm having the same problem :(

[lgenzelis]

Same issue here :(

I have this as the first line in my Dockerfile

FROM cypress/included:9.6.1 AS base

and I get the qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped errors

[goldylucks]

Based on @pladaria 's comment, I updated the chromium version and pushed to docker hub.

https://hub.docker.com/repository/docker/adamgoldman/cypress-m1

$ docker run --platform linux/arm64 -it -v $PWD:/e2e -w /e2e adamgoldman/cypress-m1

Let me know if you run into any issues

[desprit]

@goldylucks

I tried to use your image but having this error when running cypress:

qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory
Platform: linux-x64 (Debian - 11.1)

My Dockerfile:

FROM --platform=linux/arm64 adamgoldman/cypress-m1

WORKDIR /root/app
COPY yarn.lock /root/app/yarn.lock
COPY package.json /root/app/package.json
RUN yarn --frozen-lockfile

CMD ["yarn", "test-update-screenshots"]

[blvdmitry]

Has anyone published an m1 image working with cypress 10 already? Not to duplicate any existing image

[ki504178]

@goldylucks
I have tried yarn test-cypress-dev --skip-css with VSCode + Remote Container configuration and am getting the exact same error as @desprit.
The assumption is that before the above error occurred, yarn install was terminating with an error related to chromium-broswer in pupeteer, so I put a setting in the Dockerfile not to run the chrome installation. (reference)

My Dockerfile:

FROM --platform=linux/arm64 adamgoldman/cypress-m1

# Have Puppeteer skip the local Chromium download step
ENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD true

# The path where we install Chromium manually
ENV PUPPETEER_EXECUTABLE_PATH "/usr/bin/chromium"

RUN apt-get -y update && apt-get -y install chromium

Output:

root@2d994d1f943c:/workspaces/eui# yarn cypress version
yarn run v1.22.15
$ /workspaces/eui/node_modules/.bin/cypress version
Cypress package version: 9.5.4
Cypress binary version: 9.5.4
Electron version: 15.3.5
Bundled Node version: 16.5.0
Done in 1.55s.
root@2d994d1f943c:/workspaces/eui# yarn test-cypress-dev --skip-css
yarn run v1.22.15
$ node ./scripts/cypress --dev --skip-css
Not compiling SCSS, disabled by --skip-css
Opening cypress
cross-env THEME=light BABEL_MODULES=false NODE_ENV=cypress_test cypress open-ct
It looks like this is your first time using Cypress: 9.5.4


Cypress failed to start.

This may be due to a missing library or dependency. https://on.cypress.io/required-dependencies

Please refer to the error below for more details.

----------

qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory

----------

Platform: linux-x64 (Debian - 11.1)
Cypress Version: 9.5.4
node:child_process:903
    throw err;
    ^

Error: Command failed: cross-env THEME=light BABEL_MODULES=false NODE_ENV=cypress_test cypress open-ct
    at checkExecSyncError (node:child_process:826:11)
    at execSync (node:child_process:900:15)
    at Object.<anonymous> (/workspaces/eui/scripts/cypress.js:54:1)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:17:47 {
  status: 1,
  signal: null,
  output: [ null, null, null ],
  pid: 6327,
  stdout: null,
  stderr: null
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
root@2d994d1f943c:/workspaces/eui# 

[rnunezil]

I am trying to run the cypress/included 10.2.0. and get that qemu core dump error on my M1. I thought 10.2.0 was built natively on M1/arm?

docker run --platform linux/amd64 -it -v $PWD:/e2e -w /e2e cypress/included:10.2.0
Unable to find image 'cypress/included:10.2.0' locally
10.2.0: Pulling from cypress/included
c229119241af: Pull complete 
c03975a82305: Pull complete 
c85216783a8b: Pull complete 
ae04e9659b22: Pull complete 
6805f633ace3: Pull complete 
9e4968517dd3: Pull complete 
95d6aadd836f: Pull complete 
45b4738dac4b: Pull complete 
55cc9b3469f4: Pull complete 
466b5f74e6b5: Pull complete 
a102f0b6c3f5: Pull complete 
a6fd00b304f7: Pull complete 
195b0f01bbff: Pull complete 
3ce007be0b82: Pull complete 
e75892fcdc1b: Pull complete 
0919fb3d4865: Pull complete 
6079897257a9: Pull complete 
6cf4c11f1729: Pull complete 
01e69b4c320e: Pull complete 
842bea64c547: Pull complete 
Digest: sha256:5898e749826afe75cc3d017e24cb7220330b28011aa5e490534b47dede335824
Status: Downloaded newer image for cypress/included:10.2.0
2022-06-26T19:41:18.156073174-04:00 image pull cypress/included:10.2.0 (name=cypress/included)
2022-06-26T19:41:18.625743049-04:00 container create de07f67cfb44797e929f20992650482639567f24cca2828c89198fb025a7706f (desktop.docker.io/binds/0/Source=/Users/<user>/Downloads/cypress-docker-images-master/included/10.2.0, desktop.docker.io/binds/0/SourceKind=hostFile, desktop.docker.io/binds/0/Target=/e2e, image=cypress/included:10.2.0, name=hopeful_jones)
2022-06-26T19:41:18.630665632-04:00 container attach de07f67cfb44797e929f20992650482639567f24cca2828c89198fb025a7706f (desktop.docker.io/binds/0/Source=/Users/<user>/Downloads/cypress-docker-images-master/included/10.2.0, desktop.docker.io/binds/0/SourceKind=hostFile, desktop.docker.io/binds/0/Target=/e2e, image=cypress/included:10.2.0, name=hopeful_jones)
2022-06-26T19:41:18.675803132-04:00 network connect b095301ba12bb5146125dcdd95a61c42767ab9b039795b31a4fe13fa257c86ce (container=de07f67cfb44797e929f20992650482639567f24cca2828c89198fb025a7706f, name=bridge, type=bridge)
                                                       2022-06-26T19:41:18.860036216-04:00 container start de07f67cfb44797e929f20992650482639567f24cca2828c89198fb025a7706f (desktop.docker.io/binds/0/Source=/Users/<user>/Downloads/cypress-docker-images-master/included/10.2.0, desktop.docker.io/binds/0/SourceKind=hostFile, desktop.docker.io/binds/0/Target=/e2e, image=cypress/included:10.2.0, name=hopeful_jones)
    2022-06-26T19:41:18.866498966-04:00 container resize de07f67cfb44797e929f20992650482639567f24cca2828c89198fb025a7706f (desktop.docker.io/binds/0/Source=/Users/<user>/Downloads/cypress-docker-images-master/included/10.2.0, desktop.docker.io/binds/0/SourceKind=hostFile, desktop.docker.io/binds/0/Target=/e2e, height=37, image=cypress/included:10.2.0, name=hopeful_jones, width=82)
                                                         qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
The Test Runner unexpectedly exited via a exit event with signal SIGSEGV

[corysimmons]

@flotwig Awesome work on cypress-io/cypress#22252 !! 😍

I see it's merged into develop but not on DockerHub yet. If you need beta testers I'd be happy to try to do a local build and tinker with it if you can provide some instructions to do the build.

[flotwig]

@rnunezil We are still working on the multi-arch image support - Cypress 10.2.0+ is available on linux-arm64 and darwin-arm64, but we do not yet have the corresponding Docker images built and pushed to Hub/ECr. PR is ready for review so it should be available soon: #700

[flotwig]

Hi folks, our automations have been updated to issue arm64 builds with new Docker images. We will manually add arm64 builds to the latest Docker images available, but will not go back in time to add arm64 to all Docker images. I will post here when this manual work is completed. To re-iterate - arm64 images are not yet available on Docker Hub.

[flotwig]

linux/arm64 builds for the following images are now available on Docker Hub and Amazon ECR:

• cypress/base:16
• cypress/base:16.14.2-slim
• cypress/browsers:latest
• cypress/browsers:node16.14.2-slim-chrome100-ff99-edge
• cypress/included:10.3.0

Going forward, all new images will have linux/arm64 builds available. We don't plan to go back and add arm64 to any other old images at this time.

If you encounter any issues specific to the arm64 Docker builds, please check this repo for issues and if one doesn't exist, open an issue.

The only known issue at this time is that Electron is the only available browser on these images. See #695 for details.

[desprit]

I'm trying to use the cypress/included:10.3.0 image but still getting the error mentioned above #431 (comment)

qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory

FROM --platform=linux/arm64 cypress/included:10.3.0

[flotwig]

Hey @desprit, I haven't been able to reproduce this on my system, cross-building for arm64 from x64. Are you trying to cross-build an image without https://github.com/tonistiigi/binfmt? Otherwise, can you please open a new issue to track this?

[desprit]

@flotwig I'm on m1 and ideally would like to build for a regular ubuntu which I assume is linux-x64, because that's what runs on our CI servers. I tried different options just to see how it goes and results are:

--platform=linux/x86_64 - [FAILED] qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
--platform=linux/amd64 - [FAILED] qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
--platform=linux/arm64 - qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory

No, I'm not using binfmt, have never heard of it!

[flotwig]

@desprit maybe try setting up binfmt, it sets up qemu so you can cross-build for amd64 from arm64. *Also, QEMU can't run Chromium, so trying to actually run Cypress within this emulation layer will always crash. Your M1 can only run the native arm64 Cypress in a Docker image.

If you're not running Cypress in the emulation layer but you're still having this problem, can you open a new issue with your Dockerfile and the command you're running? I can try to repro on my M1, but I haven't been able to cause this error yet with what I've tried.

---

I'm going to lock this thread since linux/arm64 builds are now available on Hub and ECR for latest+future images, and comments here generate notifications for a lot of people. Please open a new issue if you are experiencing a new issue with the arm64 images.