PermissionDenied

[Joly0]

Description

I try to start Lodestone docker, but i get this error when starting:

The application panicked (crashed).
Message:  called `Result::unwrap()` on an `Err` value: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }
Location: src/prelude.rs:71

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

Steps to reproduce (optional)

Start lodestone with the provided commands from the documentation

[pinnouse]

Can you explain more about how you got to the error?
Could it be that you are pointing the docker image to a volume/location you don't have permission for?

[Joly0]

Hey, ofc. I used this command to run lodestone:

docker run -d --name='Lodestone' -p '16662:16662/tcp' -v '/appdata/lodestone':'/home/user/.lodestone':'rw' 'ghcr.io/lodestone-team/lodestone_core'

the folder /appdata already exists, /appdata/lodestone doesnt, so i let docker create it on its own. Usually for other dockers this isnt an issue, but i checked and gave the folder 777 permissions and then lodestone started and worked witohut an issue. But i havent seen such an issue with other containers yet. The default permission after creating for that folder was 755

[pinnouse]

Seems like this might be more of a docker related issue since I imagine the folder creation would be how docker chooses to handle that

[Joly0]

Its just weird, that i dont have such issues with any other docker container, just with Lodestone

[mstrlargo]

@Joly0 I was having the same issue. I am running Unraid and had an issue with another docker container that would not start until I manually created the folder. I have found that creating the folder via windows resolves the issue.

[pinnouse]

May be due to docker container using user. Perhaps we should chown the folder in the dockerfile