Do rebinds need to be in the absolute root?

[niddelicious]

I'm trying to rebind Murderbot 1 from the Dramatization edition that Bindery thinks it has to the regular Audiobook that it does have, but I'm confused by the error.
Does this not say that /books_drive/Audiobooks/ is out of bounds and then lists /books_drive/Audiobooks/ as one of the valid roots?
Am I misunderstanding this?

Running in a docker container and WLS with E:/ bound as a volume to /books_drive/

[vavallee]

Thanks for the screenshot, that made it clear. The path in the error is inside the /books_drive/Audiobooks root, so you read it right and the message is misleading. When Bindery can't open the file at all (it was renamed or moved, the drive isn't mounted, or the folder isn't readable), it used to say "outside the configured library roots", the same words it uses for a real escape. A fix is merged that says "Bindery cannot read this file" and names the file instead. It will be in the next release.

Until then, here is how to find the real cause:

1. Check that exact file exists under the same path from inside the container. What matters is the container's view, not the Windows one.
2. Run docker exec -it bindery ls -l "/books_drive/Audiobooks/Martha Wells/The Murderbot Diaries/Book 1 - All Systems Red/". If the image has no ls, check the bind mount instead.
3. Compare the file name letter for letter, including capitals, accents and any trailing space or dot. Bindery may still remember an older name.
4. If E:/ was unmounted, went to sleep or was remounted while the container ran, restart the container so the bind mount is fresh.
5. Make sure the user in your Compose file (user: "UID:GID") can read the folders and the file.
6. If the file was renamed or moved, use Forget this file on the book and scan again so the new name is registered.

If everything checks out and it still fails, post the exact message after updating and I'll look again.