Docker - Failed to create parent directories for [/config/logs/komga.log] (No such file or directory)

[RiQuY]

Steps to reproduce

Copy the docker compose file with this config and run it.

---
version: '3.3'
services:
  komga:
    image: gotson/komga
    container_name: komga
    volumes:
      - ./config:/config
      - ./data:/data
    ports:
      - 25600:25600
    user: ${PUID}:${PGID}
    # remove the whole environment section if you don't need it
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      # - <ENV_VAR>=<extra configuration>
    restart: unless-stopped

Expected behavior

The container should be able to create files inside the config and data folders.

Actual behavior

The data and config folders are created but they are empty and the docker logs shows error (check log).

• Failed to create parent directories for [/config/logs/komga.log] (No such file or directory)
• [FILE] - Attempted to append to non started appender [FILE].
• ApplicationContextException: Unable to start web server
• [SQLITE_CANTOPEN] Unable to open the database file (unable to open database file)

Logs

Logs attached as a file:

docker_logs.txt

Komga version

1.24.3

Operating system

openmediavault 7.7 (Based on Debian 12)

Installation method

Docker

Other details

I've looked at other closed issues with similar errors but I wasn't able to implement a fix by myself. I've also checked the Parameters section in the docs about environment variables and the FAQ.

I also tried using the following docker-compose config, with the same result.

• The ${PUID} and ${PGID} variables are valid I used them in others deployments to indicate the container the user ID and group ID
• The paths ./config and ./data paths are valid paths, when deploying the docker-compose file the folders are automatically created next to the komga.yml file (equivalent to docker-compose.yml), check the ls -la comand output below.

---
version: '3.3'
services:
  komga:
    image: gotson/komga
    container_name: komga
    volumes:
      - type: bind
        source: ./config
        target: /config
      - type: bind
        source: ./data
        target: /data
    ports:
      - 25600:25600
    user: ${PUID}:${PGID}
    # remove the whole environment section if you don't need it
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      # - <ENV_VAR>=<extra configuration>
    restart: unless-stopped

ls -la command output. For context, I've checked other deployments like Jellyfin and the config folders are also owned by root and in that deployment the container is able to create files inside it.

root@openmediavault:/media/Datos/Contenedores/appdata/komga# ls -la
total 32
drwxrwx---  4 root users   7 abr 14 04:52 .
drwxrwsr-x 16 root users  17 abr 14 04:39 ..
-rw-rw----  1 root users 178 abr 14 04:52 compose.override.yml
drwxr-xr-x  2 root root    2 abr 14 04:52 config
drwxr-xr-x  2 root root    2 abr 14 04:52 data
-rw-rw----  1 root users 199 abr 14 04:52 komga.env
-rw-rw----  1 root users 727 abr 14 04:52 komga.yml

Acknowledgements

• I have searched the existing issues (open AND closed) and this is a new ticket, NOT a duplicate or related to another open issue.
• I have written a short but informative title.
• I have checked the FAQ.
• I have updated the app to the latest version.
• I will fill out all of the requested information in this form.

[gotson]

you need to make sure the user running docker has the rights on the /config folder. If you don't use the bind mounts syntax, the docker daemon will use root to create the directory, but your user will not have access.

[RiQuY]

Are you suggesting that I need to create the folders manually and then deploy docker-compose using bind mounts? If that's the case I don't remember having to do this with other docker deployments of other services.

EDIT: Even when manually changing the pid:gid to match root:users the komga logs still shows the same errors, I assume the container is not using this variable even when it is included in the docker-compose.yml as user: ${PUID}:${PGID}

Screenshots attached showing my permission configuration.

(appdata is the komga parent folder)

[gotson]

you didn't read what i wrote.

You used shorthand form for the volumes:

volumes:
      - ./config:/config

if the folder does not exist, docker daemon will create it, but usually runs as root.

drwxr-xr-x  2 root root    2 abr 14 05:46 config

Then you run the container with another user, which cannot write to that folder.

You need to sort out your permissions, that's all.

[RiQuY]

you didn't read what i wrote.

You need to sort out your permissions, that's all.

I've read your message, the point is that I don't think is an issue on my end, rather than a missconfiguration inside the komga project, because like I mentioned I didn't have to mess with the permissions in any other docker deployment I have in this machine, (I'm running around 10 deployments).

As you suggested to solve the issue I had to to do the following manually:

chgrp users config/
chgrp users data/

chmod g+w config/
chmod g+w data/

I think this should be handled automatically by the docker deployment like every other app does, I'll save that workaround to make it work if it happens again, thank you for the help.

[gotson]

it's a docker thing, nothing to do with Komga. That's just how docker behaves. You didn't follow the Komga template that uses explicit bind syntax, instead you used the short syntax which has a side effect.