question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

E2E test fails in Docker locally due to missing "libelf.so.1"

See original GitHub issue

Is this a bug report?

Yes.

Can you also reproduce the problem with npm 4.x?

I can reproduce in v3.10.3 and v4.6.1.

Which terms did you search for in User Guide?

“e2e”, “docker”, “libelf”

Environment

  1. node -v: v6.3.1
  2. npm -v: 4.6.1
  3. create-react-app version: commit 7796c94

Then, specify:

  1. Operating system: Mac OS X v10.12.5
  2. Docker version: 17.06.0-ce-mac18

Steps to Reproduce

  1. Clone create-react-app from master
  2. Run npm install
  3. Run npm e2e:docker

Expected Behavior

The end-to-end test script should run in Docker and pass.

Actual Behavior

After running for a while, the test script exits with this error message:

> react-error-overlay@1.0.8 test /home/node/create-react-app/packages/react-error-overlay
> flow && jest

/home/node/create-react-app/packages/react-error-overlay/node_modules/flow-bin/flow-linux64-v0.46.0/flow: error while loading shared libraries: libelf.so.1: cannot open shared object file: No such file or directory
npm info lifecycle react-error-overlay@1.0.8~test: Failed to exec test script
npm ERR! Test failed.  See above for more details.
++ set +x
e2e-simple.sh: ERROR! An error was encountered executing line 132.
Cleaning up.
Exiting with error.

✘ Job failes
✨  Done in 119.36s.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:11 (11 by maintainers)

github_iconTop GitHub Comments

3reactions
viankakrisnacommented, Jun 29, 2017

This issue is tracked in https://github.com/nodejs/docker-node/pull/363, I believe upgrading flow to 0.48.0 in react-error-overlay will fix this. It’s still uses 0.46.0

0reactions
dallonfcommented, Jun 29, 2017

I can confirm this fix works! Thank you 🎉

Read more comments on GitHub >

github_iconTop Results From Across the Web

Run your tests
There are unit tests, integration tests and end-to-end testing. In this guide we take a look at running your unit tests in Docker....
Read more >
How To Run End-to-End Tests Using Playwright and Docker
In this tutorial, you will set up an environment to use Playwright with Typescript for end-to-end testing, write and execute the tests, ...
Read more >
Docker/Cypress Container Failing Due to Qemu Error on ...
I assume that the image pulled from the Cypress Docker repository dictates the architecture used as opposed to my --platform flag? If so,...
Read more >
Run Cypress with a single Docker command
1 image. Let's run our tests using Firefox browser for example: $ docker run -it -v $PWD:/e2e -w /e2e cypress/included ...
Read more >
How to troubleshoot Docker problems
docker login docker.art.local · 401 · HTTP code should be expected if Artifactory does not allow anonymous access to the repository in question....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found