Closed Aiakio closed 10 months ago
Try wrapping the path with quotes. The space and special character in the path might be throwing it off.
Thank you for your suggestion, @DieselTech.
I tried the following now:
Media & Books
to just Books
)I tested both of these separately, as well as combined and redeployed the updated compose file each time accordingly, of course.
Sadly it did not help. Exactly the same issues still.
Logs could help.
Updated the original post with the logs. Also here the log as a file: _komga_logs.txt
Im not sure if i'm doing something wrong here, or if there is some other issue. I can access
/volume1/Media
with other docker containers just fine.
This cannot work, you have not mounted that folder in the container, so it won't exist inside the container.
Folder is not accessible: /data
This probably means that the user running the container does not have access to the mounted folder.
Check that user 1026 can access this.
Im not sure if i'm doing something wrong here, or if there is some other issue. I can access
/volume1/Media
with other docker containers just fine.This cannot work, you have not mounted that folder in the container, so it won't exist inside the container.
This my be a stupid question, but how do i do that exactly?
I thought - /volume1/Media/Books & Manga:/data
mounts the folder?
Folder is not accessible: /data
This probably means that the user running the container does not have access to the mounted folder.
Check that user 1026 can access this.
I saw that as well, but it doesn't make sense. 1026 is my (administrator) account. My user account 1026 definitely has access rights. 1026 also works with other containers that access the /volume1/Media share.
@Aiakio
I thought
- /volume1/Media/Books & Manga:/data
mounts the folder?
It mounts the left-hand side directory as /data inside the container, so there is no /volume1/Media inside the container (it can only see /data). Having said that, your original /data/Manga
should've worked given that you've said /volume1/Media/Books & Manga/Manga
is a valid folder that contains your manga outside of the container.
Removed the special characters and spaces (renamed Media & Books to just Books)
Wasn't this Books & Manga for your original directory?
In general, it seems like you have some permission issues to solve than anything else.
your original
/data/Manga
should've worked given that you've said/volume1/Media/Books & Manga/Manga
is a valid folder that contains your manga outside of the container.
Thank you for confirming that. That is how i expected it to work, but i wasnt sure.
Removed the special characters and spaces (renamed Media & Books to just Books)
Wasn't this Books & Manga for your original directory?
Yes, this was just for testing if the &
is the problem. so i renamed the path to /volume1/Media/Books/Books
temporarily. Since this didnt change anything, i renamed it back to its original value.
In general, it seems like you have some permission issues to solve than anything else.
I have figured out what the issue was. It was the user line in the docker compose file: user: 1026:100
.
After removing said line and instead adding the user/permissions as an environment variable
environment:
- PUID=1026
- PGID=100
it works like a charm. Thank you for your assistance though.
adding the user/permissions as an environment variable
Those don't so anything in the Komga container. It's used in lsio containers, but not in Komga. Your container is thus running as root, which kinda proves that you have permission issues in the first place.
I have figured out what the issue was. It was the user line in the docker compose file:
user: 1026:100
.
You might want to enclose the value in quotes (a la user: "1026:100"
) and try again (not that it should change anything); and like Gotson said, the variables are unused for the Komga container so it's running as root. You might also want to recheck the ownership on your files.
I figured it out. It works now with user privileges and the "user:" line. I configured a regular user account in synology dsm without admin rights and access to the media & docker share (for the komga config) and then used that one for komga.
Steps to reproduce
Hello,
this is my docker compose code for komga:
My Books are stored at: /volume1/Media/Books & Manga/Books and Manga are stored at: /volume1/Media/Books & Manga/Manga
Im not sure if i'm doing something wrong here, or if there is some other issue. I can access
/volume1/Media
with other docker containers just fine.If i put
/data
inRoot folder
i can create the library, but i get a redUnavailable
message right under it.If i put
/data/Manga
or/volume1/Media/Books & Manga/Manga
inRoot folder
i get aAn error occurred while trying to update library 'XXXXXXXXXXXXX': Library root folder does not exist: file:/data/Manga
Expected behavior
That my books and mangas would show up.
Actual behavior
Red error message: "Unavailable".
Logs
Komga version
v131
Operating system
Synology DSM 7.2 / Docker
Other details
The FAQ link is dead.
Acknowledgements