-
-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing write permissions for SQLite database #332
Comments
I am also facing this problem. |
Did my workaround work for you? |
I will attempt your steps and post update here. @TheFrazer |
@TheFrazer Your suggestion seems to be working. Thanks again. |
@TheFrazer With your instructions I have successfully deployed LinkAce with SQLite. Please check this.
Please suggest any changes. |
That's how my SQLite Setup looks like as well 👍 |
I tried to run this : When i add : Perhaps |
When you add the But I have to agree with you that the permissions should ideally be checked and corrected in the |
@TheFrazer @Kovah |
Should be solved with the release of LinkAce 2.0 |
While setting up LinkAce I wanted to try SQLite, so I could skip the big db-server. When everything was running I got an error stating that the database is read only. After some searching I found this post which states:
Since the server (I'm using the simple version right now) is run with the uid/gid 82 and the whole filesytem structure is owned by root:root this only works, when you mount a directory with write access for 82 (or write access for others) and the database.sqlite inside with write access as well instead of just the database.sqlite.
So you would either need to fix the folder permissions in the docker image (or at least the database folder) or change the documentation. Something along those lines should work:
and then the docker mount would be:
and in the
.env
file it should stateDB_DATABASE=/app/database/db/database.sqlite
.I wrote this from the top of my head and didn't test it again! So please verify it again :)
Should also be the solution to #327
The text was updated successfully, but these errors were encountered: