[BUG] Failed to launch the browser process in Docker due to dbus connection failure

Issue tracker is ONLY used for reporting bugs. New features should be discussed in our Discord server.

Describe the bug The docker image doesn't function in non-dbus environment like a docker container. In the same sense, steel-browser cannot function on non-desktop servers as well.

To Reproduce Just run

docker run -p 3000:3000 -p 9223:9223 ghcr.io/steel-dev/steel-browser

Then check the container logs.

Expected behavior No Dbus dependency, and the browser init should go smoothly.

Screenshots See attached log text.

log.txt

Server (please complete the following information):

• OS: Ubuntu 22.04
• Browser: Chromium (in container image)
• Version: Latest docker image with sha256

1c988dc8a8eda687648d1c94e10e8b8627343977119f09aa34a6adf345ba104d