mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #602] Bugfix: Docker container fails due to wrong chromium path #1885
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#1885
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bash-stack on GitHub (Jan 6, 2021).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/602
had to execute
docker exec -it archivebox_archivebox_1 "ln -s /usr/bin/chromium /usr/bin/chromium-browser"@pirate commented on GitHub (Jan 6, 2021):
Can you post the exact error output you saw and the output of running
docker run archivebox/archivebox version.@bash-stack commented on GitHub (Jan 6, 2021):
sorry , i cannot remember exactly , it was the usual message when there is a binary missing in PATH ( Command not found)
( it happened on aarch64 docker version)
@pirate commented on GitHub (Jan 6, 2021):
We need the command you ran and the exact error output to reproduce it and begin figuring out what caused it. (also don't redact the output of
archivebox version, the whole output is important for us to be able to reproduce bug reports)@bash-stack commented on GitHub (Jan 8, 2021):
it is the following (aarch64) docker container:
archivebox/archivebox latest fed7c56b810d 4 weeks ago 1.08GBand happened during
archivebox add https://yourlink.net@pirate commented on GitHub (Jan 8, 2021):
Are you able to reproduce it reliably with the latest version https://github.com/ArchiveBox/ArchiveBox/releases/tag/v0.5.3? If so please post a screenshot or verbatim copy paste of the full log output while it's happening (no redactions).
This is what the full output of

archivebox versionlooks like:It provides a lot of diagnostic info about your setup that makes it much easier to help debug stuff (including certain info that only displays if you have specific runtime setups, e.g. details about your docker env). If you're able to reproduce it on the latest version please also post the verbatim output of
archivebox versionin your env, we need all this info to continue helping.