Permission denied upon start

[mzhang28]

I launched it wiht this docker compose config:

services:
  server:
    image: ghcr.io/orhun/rustypaste/rustypaste:0.16.1
    container_name: rustypaste
    restart: always
    environment:
      - RUST_LOG=debug
    env_file:
      - ./.env
    ports:
      - "10028:8000"
    volumes:
      - ./docker-data/upload/:/app/upload
      - ./config.toml:/app/config.toml

and got these errors

❯ docker compose logs
rustypaste  | Error: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }
rustypaste  | Error: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }
rustypaste  | Error: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }

no idea where this one is coming from. even with trace, there's only the correctly-parsed config file and this error and that's it. The app is crashing on start

[mzhang28]

oh upon a bit of further digging, seems like this is because of the USER 1000:1000 in the Dockerfile

[tessus]

Hmmm, I'm just wondering, if we should add this to the README. On the other side, the USER directive is quite common to additionally secure docker deployments.
I am worried that if we add "standard" stuff to the readme, it will explode at one point.

It's probably better to add a wiki FAQ page and people can add their Qs and As. ;-)

@orhun I can't get into the repo's settings. Can you enable the wiki for this repo?

[orhun]

I'd prefer we have all the documentation in the README.md instead of splitting it up at multiple places. I believe we could add FAQ to README.md as well

[mzhang28]

For my use case, I think the solution was just to create the uploads directory before actually starting the docker compose for the first time. This way, the uploads directory would not be owned by root when docker compose creates it

[tessus]

@orhun at which level? same level as Features, Installation, and Usage or under Usage? What do you think?

@mzhang28 do you want to give it a go and add a FAQ with your use-case?

[orhun]

I think FAQ section should be at the end