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

Error: Failed to launch the browser process! (solved) #329

Open
ErunamoJAZZ opened this issue Jan 5, 2024 · 0 comments
Open

Error: Failed to launch the browser process! (solved) #329

ErunamoJAZZ opened this issue Jan 5, 2024 · 0 comments

Comments

@ErunamoJAZZ
Copy link

Hello.

Recently I was trying to up this project with docker-compose, but I got the next error:

Creating whatsapp-chatgpt ... done
Attaching to whatsapp-chatgpt
whatsapp-chatgpt    | 
whatsapp-chatgpt    | > [email protected] start
whatsapp-chatgpt    | > npx vite-node src/index.ts
whatsapp-chatgpt    | 
whatsapp-chatgpt    | 
whatsapp-chatgpt    |  Whatsapp ChatGPT & DALL-E 
whatsapp-chatgpt    | |-------------------------------------------------------------------------------------------------|
whatsapp-chatgpt    | | A Whatsapp bot that uses OpenAI's ChatGPT and DALL-E to generate text and images from a prompt. |
whatsapp-chatgpt    | |-------------------------------------------------------------------------------------------------|
whatsapp-chatgpt    | 
whatsapp-chatgpt    | (node:31) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.
whatsapp-chatgpt    | 
whatsapp-chatgpt    | Please migrate your code to use AWS SDK for JavaScript (v3).
whatsapp-chatgpt    | For more information, check the migration guide at https://a.co/7PzMCcy
whatsapp-chatgpt    | (Use `node --trace-warnings ...` to show where the warning was created)
whatsapp-chatgpt    | /app/node_modules/whatsapp-web.js/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:241
whatsapp-chatgpt    |             reject(new Error([
whatsapp-chatgpt    |                    ^
whatsapp-chatgpt    | 
whatsapp-chatgpt    | Error: Failed to launch the browser process!
whatsapp-chatgpt    | [0105/014936.641153:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
whatsapp-chatgpt    | [0105/014936.641243:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
whatsapp-chatgpt    | [0105/014936.641977:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /tmp/.org.chromium.Chromium.GxYafi failed: Read-only file system (30)
whatsapp-chatgpt    | [0105/014936.642029:ERROR:platform_shared_memory_region_posix.cc(253)] Unable to access(W_OK|X_OK) /tmp: Read-only file system (30)
whatsapp-chatgpt    | [0105/014936.642060:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /tmp/.org.chromium.Chromium.dPRjTV failed: Read-only file system (30)
whatsapp-chatgpt    | 
whatsapp-chatgpt    | 
whatsapp-chatgpt    | TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
whatsapp-chatgpt    | 
whatsapp-chatgpt    |     at onClose (/app/node_modules/whatsapp-web.js/node_modules/puppeteer/src/node/BrowserRunner.ts:268:9)
whatsapp-chatgpt    |     at ChildProcess.<anonymous> (/app/node_modules/whatsapp-web.js/node_modules/puppeteer/src/node/BrowserRunner.ts:255:61)
whatsapp-chatgpt    |     at ChildProcess.emit (node:events:529:35)
whatsapp-chatgpt    |     at ChildProcess.emit (node:domain:489:12)
whatsapp-chatgpt    |     at Process.ChildProcess._handle.onexit (node:internal/child_process:292:12)
whatsapp-chatgpt    | 
whatsapp-chatgpt    | Node.js v18.19.0

It not was obvious at the start, but the read_only in docker-compose.yml was the cause.

I am not sure it is a real bug, but I just want to help if someone get this same error in the future.

Peace :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant