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

browse_website -> Chrome failed to start: exited abnormally #2304

Closed
moltra opened this issue Apr 18, 2023 · 5 comments
Closed

browse_website -> Chrome failed to start: exited abnormally #2304

moltra opened this issue Apr 18, 2023 · 5 comments
Labels
bug Something isn't working function: browse

Comments

@moltra
Copy link

moltra commented Apr 18, 2023

Is there a reason that everything says to run this is "docker-compose run auto-gpt". This does run and works great, with a few limitations. The way I understand it is that "docker-compose run auto-gpt" does not create any ports specified in the docker compose file and this would prevent accessing it from a separate computer on the network. The Docker documentation does not say that it prevents creating Volumes, but I tried the new Docker-compose file from another issue I was referred to #1843. None of the volumes were created. I also was getting errors that chrome could not open, and that the files were not

SYSTEM: Command browse_website returned: Error: Message: unknown error: Chrome failed to start: exited abnormally. (chrome not reachable) (The process started from chrome location /usr/bin/chromium is no longer running, so ChromeDriver is assuming that Chrome has crashed.) Stacktrace: #0 0x55ee1c42ffe3 #1 0x55ee1c16ed36 #2 0x55ee1c197b20 #3 0x55ee1c193a9b #4 0x55ee1c1d5af7 #5 0x55ee1c1d511f #6 0x55ee1c1cc693 #7 0x55ee1c19f03a #8 0x55ee1c1a017e #9 0x55ee1c3f1dbd #10 0x55ee1c3f5c6c #11 0x55ee1c3ff4b0 #12 0x55ee1c3f6d63 #13 0x55ee1c3c9c35 #14 0x55ee1c41a138 #15 0x55ee1c41a2c7 #16 0x55ee1c428093 #17 0x7faf347e9ea7 start_thread

SYSTEM: Command read_file returned: Error: [Errno 2] No such file or directory: '/home/appuser/auto_gpt_workspace/search_results.txt'

Not sure if these are related or not. If not I will split these items into separate issues.

@Pwuts
Copy link
Member

Pwuts commented Apr 18, 2023

I'm not sure what's going on for you (post your log!), but the volume mounts generally work fine using docker-compose run. Also, we currently don't see a need to expose ports on the container. Its only purpose is to be a sandbox to protect the host machine.

@ntindle
Copy link
Member

ntindle commented Apr 18, 2023

Unless your docker compose adds a selenium standalone chrome instance, I'd be pretty surprised if that worked in the container.

See #1843 (comment)

@k-boikov
Copy link
Contributor

Might be fixed with #1473

@k-boikov
Copy link
Contributor

Similar to #1641

@Pwuts Pwuts changed the title Docker-compose run vs "up -d" browse_website -> Chrome failed to start: exited abnormally Apr 18, 2023
@Pwuts Pwuts added function: browse bug Something isn't working labels Apr 18, 2023
@Pwuts
Copy link
Member

Pwuts commented Apr 18, 2023

Closing as duplicate of #1641

@Pwuts Pwuts closed this as not planned Won't fix, can't repro, duplicate, stale Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working function: browse
Projects
None yet
Development

No branches or pull requests

4 participants