mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #633] Question: How to run ArchiveBox under Docker as non-root. #392
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#392
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 @thprice on GitHub (Jan 25, 2021).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/633
Actually, I run it on Kubernetes, not plain Docker (or, rather, try to run it).
When trying to initialise the archive (database etc.) using
archivebox initit fails with:
[!] ArchiveBox should never be run as root!When running the container as another user than root, it complains that it either doesn't know the user id or fails with:
error: failed switching to "archivebox": operation not permittedAny ideas?
@pirate commented on GitHub (Jan 25, 2021):
I think this is the same issue as here: https://github.com/ArchiveBox/ArchiveBox/issues/539
You can try some of the workarounds others have posted in that thread, or just subscribe and stay tuned for when a fix is pushed.
This only happens in some specific docker scenarios and I think you were unlucky enough to hit one of them. Hopefully we'll have a fix out soon, but I can't promise it'll be this week.
@thprice commented on GitHub (Jan 28, 2021):
Thanks for your response. It may be the same issue but I'm not sure. #539 is about file system access problems while this here seems to be about errors switching the uid.
No need for a reopen, though. I'll wait for the fix and try again. Maybe, I'll come back then. :-)
@pirate commented on GitHub (Jan 28, 2021):
The fix for UID/GID switching issues is the same fix as the one for #539 (I think), it's actually already on
devif you want to try it.@thprice commented on GitHub (Jan 29, 2021):
Thanks for the fix. It can confirm that it works (at least for me :-))