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.

Bug: Docker Failed to launch the browser process! spawn /usr/bin/chromium-browser ENOENT

See original GitHub issue

Describe the bug

Singlefile output doesn’t work.

Steps to reproduce

  1. Using docker-compose try to add a url with singlefile mode
  2. Fail. Try to run the command the page suggests running (/node/node_modules/single-file/cli/single-file --browser-executable-path=chromium "--browser-args=[\"--headless\", \"--no-sandbox\", \"--disable-gpu\", \"--disable-dev-shm-usage\", \"--disable-software-rasterizer\", \"--run-all-compositor-stages-before-draw\", \"--hide-scrollbars\", \"--user-agent=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.61 Safari/537.36 ArchiveBox/{VERSION} (+https://github.com/ArchiveBox/ArchiveBox/)\", \"--window-size=1440,2000\"]" https://www.kabum.com.br/ singlefile.html)
  3. Error: “Failed to launch the browser process! spawn /usr/bin/chromium-browser ENOENT”

ArchiveBox version

ArchiveBox v0.6.2
Cpython Linux Linux-5.10.0-odroid-arm64-aarch64-with-glibc2.28 aarch64
IN_DOCKER=True DEBUG=False IS_TTY=True TZ=UTC SEARCH_BACKEND_ENGINE=ripgrep

[i] Dependency versions:
 √  ARCHIVEBOX_BINARY     v0.6.2          valid     /usr/local/bin/archivebox
 √  PYTHON_BINARY         v3.9.5          valid     /usr/local/bin/python3.9
 √  DJANGO_BINARY         v3.1.10         valid     /usr/local/lib/python3.9/site-packages/django/bin/django-admin.py
 √  CURL_BINARY           v7.64.0         valid     /usr/bin/curl
 √  WGET_BINARY           v1.20.1         valid     /usr/bin/wget
 √  NODE_BINARY           v15.14.0        valid     /usr/bin/node
 √  SINGLEFILE_BINARY     v0.3.16         valid     /node/node_modules/single-file/cli/single-file
 √  READABILITY_BINARY    v0.0.2          valid     /node/node_modules/readability-extractor/readability-extractor
 √  MERCURY_BINARY        v1.0.0          valid     /node/node_modules/@postlight/mercury-parser/cli.js
 √  GIT_BINARY            v2.20.1         valid     /usr/bin/git
 √  YOUTUBEDL_BINARY      v2021.04.26     valid     /usr/local/bin/youtube-dl
 √  CHROME_BINARY         v89.0.4389.114  valid     /usr/bin/chromium
 √  RIPGREP_BINARY        v0.10.0         valid     /usr/bin/rg

[i] Source-code locations:
 √  PACKAGE_DIR           22 files        valid     /app/archivebox
 √  TEMPLATES_DIR         3 files         valid     /app/archivebox/templates
 -  CUSTOM_TEMPLATES_DIR  -               disabled

[i] Secrets locations:
 -  CHROME_USER_DATA_DIR  -               disabled
 -  COOKIES_FILE          -               disabled

Apparently it tries to run /usr/bin/chromium-browser which doesn’t exist. The correct would be /usr/bin/chromium. Either symlink it, or change the code to use /usr/bin/chromium. Thanks.

Issue Analytics

  • State:open
  • Created 2 years ago
  • Comments:8 (3 by maintainers)

github_iconTop GitHub Comments

3reactions
piratecommented, Jan 30, 2022

Maybe we can fix it with a symlink shim created in the Dockerfile that points /usr/bin/chromium-browser -> /usr/bin/chromium?

1reaction
piratecommented, Mar 13, 2022

docker-compose exec archivebox ln -s /usr/bin/chromium /usr/bin/chromium-browser for now until I add a fix to the Dockerfile later.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error: Failed to launch the browser process! spawn /usr/bin ...
I had the same issue when I was trying to run the node container in docker. My environment is using: Docker version 20.10.12;...
Read more >
Failed to launch the browser process! spawn puppeteer Code ...
Puppeteer Error on ubuntu 100% Correct Solution by Vivek wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb sudo apt install .
Read more >
Troubleshooting | Puppeteer
Starting from v19.0.0, Puppeteer will download browsers into ~/.cache/puppeteer ... Error: Failed to launch chrome! spawn /usr/bin/chromium-browser ENOENT.
Read more >
Docker: puppeteer not working on a Express (NestJS) app
Error: Failed to launch the browser process! spawn /usr/src/app/node_modules/puppeteer/.local-chromium/linux-901912/chrome-linux/chrome ENOENT Nov 19 ...
Read more >
apple m1 Error: Failed to launch the browser process spawn ...
把node_modules/puppeteer/lib/cjs/puppeteer/node/Launcher.js里面的if (os.arch() === 'arm64') { chromeExecutable = '/usr/bin/chromium-browser' ...
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