-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Use of the tool with docker issue #27
Comments
you need to specify an input folder |
Hello, See screeenshoots hereunder please : |
Let's start at the top. This is how I did my workflow 1.) Run the automated script against source folder - unorganized-books You want to have each folder you are working with mapped in the docker, or the parent folder mapped or docker won't be able to reach them externally. So if it were me, I'd create a project folder, then have your working directories there. Kind of like this:
Your docker command would look like
This would map the folder "ebooktools" on your filesystem to the folder "/organize" on the docker Load up the books you want to match into the /ebooktools/unorganized-books folder on your server.
so together this command would look like If you want to go back through and audit the matches you can use the interactive command. For this I made another folder called invalid-matches in the organize folder. This is if there is a bad match that I can't get the script to fix or match, I send those files to this folder for manual adjustment later. My interactive command has two phases. I started with the output folder, just as a sanity check
Together its Then I run Lastly, use Now you should have all your books in either Good luck! |
Hello Than you for your detailed answer, I tried: New organisation of my folders and the result in the terminal is he dont find the following directory: /organize/unorganized-books/ Than you again for your help |
will you run Also - I wonder if it has something to do with the mount path. Ideally you could run the second command and see your folders you made. |
It seem that in docker and in the folder /organize/ there is no subfolders ├── organized-books |
yeah there is something junky going on with the mapping of the path Maybe try docker run -it -v "\wsl$\Ubuntu-20.04\home\a\ebooktools:/organize" ebooktools/scripts:latest WSL is spooky |
C:\Users\djilo>docker run -it -v "\wsl$\Ubuntu-20.04\home\a\ebooktools:/organize" ebooktools/scripts:latest docker: Error response from daemon: \wsl$\Ubuntu-20.04\home\a\ebooktools%!(EXTRA string=is not a valid Windows path). |
oops! I missed a backslash. Sorry, it's late. |
I try this one If this don't work no problem than you for your help Let's see this tomorow if possible |
C:\Users\djilo>docker run -it -v "\wsl$\Ubuntu-20.04\home\a\ebooktools:/organize" ebooktools/scripts:latest docker: Error response from daemon: can't access specified distro mount service: stat /run/guest-services/distro-services/ubuntu-20.04.sock: no such file or directory. |
Looks like that command is still missing a \ on the front |
Sorry I launched this twice, with the \ on the front and the result is the same: Test 1 C:\Users\djilo>docker run -it -v "\wsl$\Ubuntu-20.04\home\a\ebooktools:/organize" ebooktools/scripts:latest Test 2 C:\Users\djilo>docker run -it -v "\wsl.localhost\Ubuntu-20.04\home\a\ebooktools:/organize" ebooktools/scripts:latest |
no, you still need the double \ use this command |
no,w you see that I used the double \ |
Hello ,
First than you for this tool to organize books. I have a huge collection of books that I want to organize so I decide to try your tool via docker because I am on windows
Image en ligne 1
Image en ligne 2
docker run -it -v //wsl$/Ubuntu-20.04/home/a:/unorganized-books ebooktools/scripts:latest
organize-ebooks.sh --output-folder=organized-books/
as result I have this
eBook Organizer v0.5.1
Usage: organize-ebooks.sh [OPTIONS] EBOOK_FOLDERS...
For information about the possible options, see the README.md file or the script source itself
5 Summary
Image en ligne 3
What I did wrong please ? Can you help me please ?
Regards
The text was updated successfully, but these errors were encountered: