mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #838] ArchiveBox should never be run as root Windows Docker create super user #520
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#520
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 @cybrpimp on GitHub (Aug 31, 2021).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/838
I've was able to install ArchiveBox on Docker without a problem from the Docker Hub download, but when I try to create a superuser I get the following error;
@likuilin commented on GitHub (Sep 1, 2021):
I got the same issue. As a workaround, you can
su archiveboxfirst and then do whatever you need to do, or you can specify the username to use to docker by doingdocker-compose exec -u archivebox archivebox archivebox create superuser@pirate commented on GitHub (Sep 8, 2021):
You should use
runnotexec, it will handle the user permissions correctly for you:@likuilin commented on GitHub (Sep 10, 2021):
Good point! Though if you do that, you're spinning up a separate docker container, so you should add
--rmor else you leave behind a stopped container that isn't cleaned up.Edit: Huh, it seems like the documentation advises using
docker-compose runbut doesn't have any--rmin its examples. That should be fixed, I think. Running the documentation examples as-is leaves stopped containers on every command, which needlessly take up space. Though, this is a separate issue.@pirate commented on GitHub (Sep 16, 2021):
In my experience they don't take up appreciable additional disk space because of docker's BTFS COW-based filesystem. If you want to clean them up you can always run
docker system prune. You're welcome to add--rm, but I don't add it to the examples/docs in order to keep them as short, simple, and intuitive as possible.