mirror of
https://github.com/matze/wastebin.git
synced 2026-04-25 16:45:59 +03:00
[GH-ISSUE #56] [HELP] need help making the database writeable by user 10001 #44
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/wastebin-matze#44
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 @back-lacking on GitHub (Jun 9, 2024).
Original GitHub issue: https://github.com/matze/wastebin/issues/56
So im trying to get wastebin running using docker compose. the main part im having trouble with is trying to make the data base writable. i tried running these commands to make the data base file writable, but all have failed
trying to run
docker compose up -dto get it up, but it wouldnt start and the logs would report that the database was read only.can I know the proper command in order to get this up and running?
@matze commented on GitHub (Jun 9, 2024):
I personally don't use docker compose but could it be that 10001 is not the correct user?
@back-lacking commented on GitHub (Jun 9, 2024):
im not sure, i was just following the default docker compose you gave. and there was a note saying "make sure ./data is writable by user 10001."
@back-lacking commented on GitHub (Jun 9, 2024):
i tried just looking up how to make a folder writable by a certain user, and the
sudo chowncommand was what i did@matze commented on GitHub (Jun 10, 2024):
I did not write those instructions but perhaps @NiFNi can help out :-)
@NiFNi commented on GitHub (Jun 10, 2024):
The UID in the Dockerfile is 10001 as you can see here:

github.com/matze/wastebin@f13fcd077b/Dockerfile (L10)Permissions like this work for me:
In case the database file is already created make sure it is also owned by 10001. Best is to just run these commands to get the default permissions:
One hint: keep in mind that a user needs executable permissions of a folder to view the content of the folder in UNIX systems. So the user 10001 has to have the read+executable permission of the data folder and the read+write permissions of the state.db file which will be achieved by the commands above.
@back-lacking commented on GitHub (Jun 11, 2024):
Running those commands fixed the issue