mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #62] Simple docker container for bookmark-archiver #3062
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#3062
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 @pirate on GitHub (Jan 10, 2018).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/62
Once the backend/proxy portion is done, many people have asked for a docker container to run it.
@aurelg commented on GitHub (Aug 29, 2018):
Here's a quick & dirty attempt from a Docker newbie:
For some reason,
chromium-browsersegfaults, though. Any idea?Edit: I forgot the to add
curl:)Edit 2: When specifying
-e FETCH_PDF=False -e FETCH_DOM=False -e FETCH_SCREENSHOT=Falseon the docker command line to skipchromiumcompletely, I noticed that theoutputdirectory is created in/bookmark-archiver(where./archiveis) although the current directory (set byWORKDIR) is/dataand is shared with the host. Maybe that's the expected default behavior ofbookmark-archiver?@pirate commented on GitHub (Aug 29, 2018):
Always creating
./outputinsidebookmark-archiver/is the expected behavior right now, but I could change it to output to current dir, I didn't do that initially because the main use case for having multiple output folders is if they were hosting this as a service, and I want to eventually do that myself and charge for it so I can fund development of this project 😁Not sure why chromium-browser is segfaulting, perhaps you can build the image on top of an already-working chromium docker image?
@aurelg commented on GitHub (Aug 30, 2018):
I haven't fixed the bug yet, but hacked my own version: linkbak.
@aurelg commented on GitHub (Sep 1, 2018):
Bug fixed on linkbak, here's the relevant Dockerfile. I ended up using another base image (
stretch-sliminstead ofalpine), but I think it's not related. I had to tweak around sandboxing (--no-sandbox) and users/permissions to make it work.@pirate commented on GitHub (Oct 14, 2018):
I've now added a Dockerfile on master that works. A docker-compose.yml example with nginx to server the archive will come next.
@pirate commented on GitHub (Oct 15, 2018):
CC: @hannah98 @ivar @ilvar @Strubbl @aurelg
You can use the new official docker image for Bookmark Archiver like so:
It's not perfect yet, I still have to make the ergonomics better for passing in link files to parse, right now you have to put them in the output volume and then reference them by their path inside the container to get BA to find them:
docker run -v archiver-output:/home/chromeuser/app/archiver/output bookmark-archiver /home/chromeuser/app/archiver/output/downloads/path-to-links.jsonYou're welcome to submit PRs if you find things that can be fixed/improved!
@pirate commented on GitHub (Jan 30, 2019):
Closing this because it's been released and working fairly well for a while now: https://github.com/pirate/ArchiveBox/wiki/Docker