Kaizoku can't create library or make directories

[SSj-Saturn]

Describe the bug

Docker install on OSX, on initial install to create a library, I'll get the following error when attempting to make /data. There's no directory browsing on this field, it's just asking for a direct path.

Failed to create library. TRPCClientError: ENOENT: no such file or directory, mkdir '/data'

docker-compose.yml below, the volume paths are local to try and diagnose, but eventually they'll go to my NAS('/Volumes/NAS\ Storage/Komga').

version: '3'

volumes:
  db:
  redis:

services:
  app:
    container_name: kaizoku
    image: ghcr.io/oae/kaizoku:latest
    environment:
      - DATABASE_URL=postgresql://kaizoku:kaizoku@db:5432/kaizoku
      - KAIZOKU_PORT=3000
      - REDIS_HOST=redis
      - REDIS_PORT=6379
      - PUID=501
      - PGID=80
      - TZ=America/Los_Angeles
    networks:
      - mynetwork
    volumes:
      - '/Users/manchesterca/Desktop/Komga:/app/manga'
      - '/Users/manchesterca/Desktop/Komga:/data'
      - '/Users/manchesterca/Desktop/Komga:/config'
      - '/Users/manchesterca/Desktop/Komga:/logs'
    depends_on:
      db:
        condition: service_healthy
    ports:
      - '3000:3000'
  redis:
    image: redis:7-alpine
    volumes:
      - redis:/data
    ports:
      - "${REDIS_PORT:-6379}:6379"
  db:
    image: postgres:alpine
    restart: unless-stopped
    healthcheck:
      test: ['CMD-SHELL', 'pg_isready -U kaizoku']
      interval: 5s
      timeout: 5s
      retries: 5
    environment:
      - POSTGRES_USER=kaizoku
      - POSTGRES_DB=kaizoku
      - POSTGRES_PASSWORD=kaizoku
    volumes:
      - db:/var/lib/postgresql/data
    ports:
      - "${DATABASE_PORT:-5432}:5432"

Reproduction steps

1. launch with above fresh docker-compose.yml
2. goto http://localhost:3000/
3. Click 'create library'
4. type '/data' (as shown by the example input).
5. observe error message.

Expected behavior

should bind and makdir as expected.

Additional context

any help appreciated here, just can't seem to get this to work!

[Underestimated]

Does your docker user (often not the same as your logon user) have permission to write to the folder? Also have you granted the docker daemon permission to access your desktop in the Mac’s Settings and Privacy options? The Mac will hide all desktop folders from the program until you do.

Ideally you shouldn’t be pointing all your volumes to a single folder like you have, you should point them to a sub folder of that top level folder that is NOT shared by any other app, otherwise you could have conflicts that block access. The only directory you should share across multiple apps itself is the manga Library one.

so your volumes should look like this:

volumes:
  - '/Users/manchesterca/Desktop/Komga/manga:/app/manga'
  - '/Users/manchesterca/Desktop/Komga/kaizoku/data:/data'
  - '/Users/manchesterca/Desktop/Komga/kaizoku/config:/config'
  - '/Users/manchesterca/Desktop/Komga/kaizoku/logs:/logs'

Make sure you create those folders before starting docker, it won’t do it for you.

I’ve nested your kaizoku data under a kaizoku folder so you should do the same thing for komga which I assume you’re running alongside this, that stops the two apps from overwriting each others data, which will happen as some file names are the same.

by doing this it should run and allow you to create libraries.

If you’re really stuck, you can always try using Portainer to manage the docker environment, it gives a web UI and a way to dynamically create volumes as needed without stuffing around with permissions.

[SSj-Saturn]

@Underestimated unfortunately, same error with these changes;

• Updated the volumes in the docker compose
• Gave Docker full Files and Folders access in Mac Security
• Created the folders within the kaizoku desktop folder.

Feels like it's something really simple and dumb that I'm missing here. Not too used to Docker or Portainer tbh, so any direction appreciated, and thank you for the navigation so far!

[Underestimated]

OK the last thing you might have missed: Right Click the folder and click Get Info go down the bottom of the info window, click on Sharing & Permissions, and set the permission for everyone to read and write (it'll probably be read only right now) this allows any authenticated account on the system to read and write the folder (Docker usually uses a hidden system account to write to folders, and your permissions at the moment will block them)

(Also when you're done if it still errors, remove the / from the front of the folder name. it might be trying to edit an area on the virtual drive it doesn't have access to edit. Another method to try is add a subfolder under /data e.g. /data/library and see if that fixes it)

You'll not have this drama when you go to a NAS usually, because the NAS doesn't apply the permissions in the same way.

[SSj-Saturn]

After all that, yup just didn't like the /data, dropping that slash and just adding data in seemed to solve it all.

Resolved, ty!