Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory

[fanshyiis]

When I'm running in a docker environment
When you launch cypress
Always report dbus error

[adomyaty55foundry]

Receiving this issue as well constantly always, I can still use cypress okay but nonetheless the error keeps coming in console

Using WSL 2 (Ubuntu 1804) + mobaXterm (X-Server)

[jennifer-shehane]

I'm not entirely sure this is a Cypress issue instead of something isolated to the docker container.

Have you tried our docker images https://github.com/cypress-io/cypress-docker-images or made sure that you have all system dependencies installed required for cypress?

[iperdomo]

Hi,

You can see the same error in this CI job execution:
https://akvo.semaphoreci.com/jobs/1be15282-d440-40da-9932-7f245d4b48a6#L452

The actual test finished successfully but the dbus error is there.

We're using a container based on the latest cypress/included:3.8.1
https://github.com/akvo/akvo-dockerfiles/blob/9f9bb5317ebbca14972424b074792f9dd0eb785c/lumen-e2e-test/Dockerfile#L3

Any hints are more than welcome

[iperdomo]

The errors are shown when ELECTRON_ENABLE_LOGGING=true environment variable is set. The tests pass successfully.

A minimum sample system that shows this error. It's using the published Docker image cypress/included:3.8.1

https://github.com/iperdomo/cypress-docker-test

In Cypress documentation site you can find the same error message:

• https://docs.cypress.io/guides/guides/debugging.html#Run-the-Cypress-app-by-itself

[iperdomo]

If you use a Linux host you expose the /var/run/dbus/system_bus_socket socket to the container and the errors go away. Disclaimer: Not entirely sure what security problems this "solution" brings.

See: https://github.com/iperdomo/cypress-docker-test#fixing-the-errors

[jennifer-shehane]

@iperdomo It also explains in the docs that these errors are fine if Cypress launches successfully.

Note: verbose Electron logging might show warnings that still allow Cypress to work normally. For example, the Cypress Test Runner opens normally despite the scary output below:

You can safely ignore the dbus error if your tests are executing fine.

[matchu]

In the case of WSL, I think this is because WSL doesn't do any system startup, so there isn't a system dbus process running!

I fixed this by added sudo dbus-daemon --system &> /dev/null to my .bashrc, based on what I found here: microsoft/WSL#2941