fix: permissions

[lklynet]

I'm trying to launch this as a completely new instance, and I get:

aurral-1 | /app/backend/node_modules/better-sqlite3/lib/database.js:69
aurral-1 | ch d Detac[util.cppdb]: { value: new addon.Database(filename, filenameGiven, anonymous, readonly, fileMustExist, timeout, verbose || null, buffer || null) },
aurral-1 | ^
aurral-1 | SqliteError: unable to open database file
aurral-1 | at new Database (/app/backend/node_modules/better-sqlite3/lib/database.js:69:26)
aurral-1 | at file:///app/backend/config/db-sqlite.js:16:12
aurral-1 | at ModuleJob.run (node:internal/modules/esm/module_job:325:25)
aurral-1 | at async ModuleLoader.import (node:internal/modules/esm/loader:606:24)
aurral-1 | at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:117:5) {
aurral-1 | code: 'SQLITE_CANTOPEN'
aurral-1 | }
aurral-1 |
aurral-1 | Node.js v20.20.0
aurral-1 exited with code 1 (restarting)

This is due to the data folder getting created as root first, but then the application drops inside as UID1001 - causing the folder not to be writable.

So best to ask people to create the folder in advance with the right permissions :-)
Also looks like running on a different port works out of the box now, great.

edit: unfortunately, for me, it seems the recommendations are broken:
aurral-1 | Found 113 artists in library.
aurral-1 | Sampling tags/genres from 25 artists (113 library, 0 Last.fm)...
aurral-1 | Found tags for 0 out of 25 artists

Originally posted by @Wireheadbe in #36

[MIPOHBOPOHIH]

oh, it looks like my error which i wrote about several days ago
https://gist.github.com/MIPOHBOPOHIH/ff83b8556c84afa418a9f6a841e369b0
what should i do to fix it? what permissions should i give to folder and can you help me with mounts in docker?
#36 (comment)

[Grrarrrgh]

oh, it looks like my error which i wrote about several days ago https://gist.github.com/MIPOHBOPOHIH/ff83b8556c84afa418a9f6a841e369b0 what should i do to fix it? what permissions should i give to folder and can you help me with mounts in docker? #36 (comment)

There's some guidance on my closed issue from yesterday:
#39

You need the make the ./data folder writeable by user 1001. Assuming you've not changed the location of the data folder you can do that like this:

cd /path/to/your/aurralcompose
chown -R 1001:1001 /data
chmod -R u+rwX /data

Then you can docker compose up -d and it should get you up and running

[MIPOHBOPOHIH]

oh, it looks like my error which i wrote about several days ago https://gist.github.com/MIPOHBOPOHIH/ff83b8556c84afa418a9f6a841e369b0 what should i do to fix it? what permissions should i give to folder and can you help me with mounts in docker? #36 (comment)

There's some guidance on my closed issue from yesterday: #39

You need the make the ./data folder writeable by user 1001. Assuming you've not changed the location of the data folder you can do that like this:

cd /path/to/your/aurralcompose
chown -R 1001:1001 /data
chmod -R u+rwX /data

Then you can docker compose up -d and it should get you up and running

idk why, but it doesnt helped, ive done almost everything

and im getting this error again

[MIPOHBOPOHIH]

okay, im deployed aurral as root. i dont think this is a good choice, but now its finally running

[Grrarrrgh]

I think you must have entered the chown incorrectly as that shows the data dir is owned by 1000 still

if you do

cd /docker/aurral
chown -R 1001:1001 /data
chmod -R u+rwX /data

Then check that data is 1001 1001 rather than 1000 users
If that's done correctly then you won't need to run it as root.