You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use the docker compose example from github page.
Bind the /data volume anywhere in the host computer.
Download any manga.
It is kept inside the container, not in the bound folder.
Expected behavior
The manga should be downloaded to the data folder instead
Additional context
No response
The text was updated successfully, but these errors were encountered:
Thanks!
Yeah, I can take them out of the container and put them in the right folder, but I'd rather not keep the data inside the container as well, since it becomes bloated after a time.
hello, is there any progress with this bug? I'm facing the same issue when using the latest tag in docker.
have binded a folder like the README.md but it defaulted to creating the new library in /app and not /data
I found a workaround.
Instead of using the mount suggested in the docker compose:
/mnt/user/Media/Books/Manga:/data
Map instead to the /app/manga folder (manga is the name of the library I created when starting kaizoku, files are downloaded there. If you use another name, change the mapping accordingly)
/mnt/user/Media/Books/Manga:/app/manga
Describe the bug
The data folder is mapped to a location in the host machine, and its contents show in the container.
/mnt/user/Media/Books/Manga:/data
However, all downloads are not saved there, but in the /app/manga folder instead (manga is the name of the library).
See reddit post for reference:
https://www.reddit.com/r/selfhosted/comments/yazsjw/kaizoku_manga_downloader/ji6eam2/
Reproduction steps
Use the docker compose example from github page.
Bind the /data volume anywhere in the host computer.
Download any manga.
It is kept inside the container, not in the bound folder.
Expected behavior
The manga should be downloaded to the data folder instead
Additional context
No response
The text was updated successfully, but these errors were encountered: