mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 09:06:02 +03:00
[GH-ISSUE #975] Bug: Can't use PUID=33 in docker #606
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#606
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 @HHousen on GitHub (May 15, 2022).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/975
Describe the bug
Creating an archivebox docker container using the
PUIDandPGIDvariables works correctly except when usingPUID=33andPGID=33(www-dataid). When using the below docker-compose configuration and runningdocker compose run archivebox init --setup, the data directory (/opt/archivebox) is owned by999:dockernotwww-data:www-data.Steps to reproduce
Use the following docker-compose configuration
I am able to use the id
33in linuxserver.io images with the samePUIDandPGIDoptions. Also, using a different id like876works as intended with the data directory being owned by876:876.ArchiveBox version
@pirate commented on GitHub (Jun 9, 2022):
I've added some more debug output to the version command to help track down the bug. Can you install from dev and post the output of
archivebox versionagain.@pirate commented on GitHub (Jan 4, 2024):
It seems like
33conflicts with an existing UID in the container. Are you able to use a different PUID? If so you can keep 33 as thePGIDso that the files are accessible bywww-dataon the host.Also please try with the latest
archivebox/archivebox:0.7.2build as I've added many helpful error messages and improved Docker permissions handling in general.