filebot / filebot-docker

Docker build files for FileBot
https://hub.docker.com/r/rednoah/filebot/
Apache License 2.0
55 stars 18 forks source link

Clarity on paths in docker container. #4

Closed bashfulrobot closed 4 years ago

bashfulrobot commented 4 years ago

Hi there,

I am running the container with:

docker run --rm -it -v $PWD:/volume1 -v data:/data rednoah/filebot -rename /home/dustin/tmp/Media/process/dl --format "{plex}" --db thetvdb --lang en --action copy --conflict override --output /home/dustin/docker/plex --log-file /home/dustin/docker/filebot/logs/FileBot.log -non-strict

When I run the command I am getting:

Locking /home/dustin/docker/filebot/logs/FileBot.log
Illegal Argument: java.nio.file.NoSuchFileException: /home/dustin/tmp/Media/process/dl (/home/dustin/tmp/Media/process/dl)
Rename episodes using [TheTVDB]
No media files: [/home/dustin/tmp/Media/process/dl]
Failure (×_×)⌒☆

Now in the dl folder, there is another folder containing the episode I am testing against.

I think I am misunderstanding how the volume maps are relevant.

Thank you.

rednoah commented 4 years ago

I'd start with a general tutorial on Docker and how file systems are isolated from each other, and how to map host file systems into the container file system: https://docs.docker.com/storage/volumes/

Specifically, in the command you are mapping your host current working directory into /volume1 inside the container via -v $PWD:/volume1. You will likely need to adjust that.

Presumably, /home/dustin/tmp/Media/process/dl is a path on your host, and doesn't exist within the container, hence NoSuchFileException. Adding -v /home/dustin:/home/dustin to the command will do the trick, but please read the manual first, so you understand why this works. ;)

rednoah commented 4 years ago

I'll close the issue here, since it's a general question on docker and rather unrelated to filebot-docker specifically.