You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Browser capture always fails: Chromium cannot start because HOME=/root is not writable for the runtime user #47
docker-entrypoint.sh drops privileges with setpriv (PUID/PGID) but keeps HOME=/root, which the runtime user cannot write.
Chromium's crash reporter then aborts at startup:
chrome_crashpad_handler: --database is required
so every browser-based capture done by easyx-browser-fetch fails with Chromium debugging page did not start. This shows up, for example, when a live stream falls back to the browser capture after yt-dlp could not resolve it.
Reproduce
Inside the running container:
docker exec -u node -e HOME=/root open-easyx easyx-browser-fetch --capture-media https://stripchat.com/
# -> Chromium debugging page did not start
Possible fix
In docker-entrypoint.sh, create a directory owned by the runtime user (e.g. /tmp/easyx-home) and export it as HOME before dropping privileges. yt-dlp and other tools also get a writable cache directory this way.
In scripts/easyx-browser-fetch.py, fall back to a per-user temporary home when HOME is not writable, so the helper also works with other launchers.
I proposed this in #43 (closed). Happy to adapt it if you prefer another approach.
This bug was found by Claude Code (Anthropic's AI coding assistant) while I was working on the project with it.
Activity