Docker: "Couldn't watch" No such file or directory.

Support for Ubuntu and other Desktop Linux distributions
Post Reply
w0wreally
Posts: 3
Joined: 17 Mar 2019, 22:44

Docker: "Couldn't watch" No such file or directory.

Post by w0wreally » 29 Apr 2019, 23:40

I bought a license recently and am trying to set up a filebot watcher in docker. It worked ONCE, but then I found that it was creating every new file as root, and I wasn't able to delete them without sudo'ing into terminal.

I tried setting -e UMASK=000 \ -e PUID=1000 \ -e PGID=1000 \ options but never got it running again.

The more noob-friendly docker tutorials include a fleshed out starter configuration. I sense I'm doing something wrong with the volume1 settings, but I can't find many docker filebot results on Google in general - and the recent results indicated that the docker build was actually 100% broken for everyone .. as recently as the 19th. Thanks for any help. My command line below:

Code: Select all

[email protected]:~/share/in$ docker run -it -v $PWD:/volume1 -v data:/data rednoah/filebot -script fn:sysinfo
FileBot 4.8.5 (r6224)
JNA Native: 5.2.2
MediaInfo: 18.03.1
p7zip: p7zip Version 16.02 (locale=C.UTF-8,Utf16=on,HugeFiles=on,64 bits,8 CPUs Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz (206D7),ASM,AES-NI)
unrar: UNRAR 5.50 freeware
Chromaprint: fpcalc version 1.4.3
Extended Attributes: OK
Unicode Filesystem: OK
Script Bundle: 2019-04-23 (r560)
Groovy: 2.5.6
JRE: OpenJDK Runtime Environment 11.0.2
JVM: 64-bit OpenJDK 64-Bit Server VM
CPU/MEM: 8 Core / 1 GB Max Memory / 19 MB Used Memory
OS: Linux (amd64)
HW: Linux 24d0afe818e3 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
DATA: /data/.filebot
Package: DOCKER
License: FileBot License (Valid-Until: 2020-03-30)
Done ヾ(@⌒ー⌒@)ノ

[email protected]:~$ cd /home/d/share/in/complete
[email protected]:~/share/in/complete$ docker run -it -v $PWD:/home/d/share/ -v data:/data rednoah/filebot:watcher /home/d/share/in/complete/ --output /home/d/share/media/
Setting up watches.
Couldn't watch /home/d/share/in/complete/: No such file or directory
[email protected]:~/share/in/complete$

Edit: this worked instead, but I am not sure why.

Code: Select all

docker run -it -v $PWD:/home/d/share/media -v data:/data rednoah/filebot:watcher /home/d/share/media/complete --output /home/d/share/media

w0wreally
Posts: 3
Joined: 17 Mar 2019, 22:44

Re: Docker: "Couldn't watch" No such file or directory.

Post by w0wreally » 30 Apr 2019, 00:36

Got it running properly with this, but it's still setting all the folder permissions to root. I think the PWD folder has to be the exact home directory to the other 2?

Code: Select all

docker run -d \
--name=filebot \
--restart=always \
-v $PWD:/home/d/share/in \
-v data:/data \
-e UMASK=000 \
-e PUID=1000 \
-e PGID=1000 \
rednoah/filebot:watcher /home/d/share/in/done \
--output /home/d/share/in/media \
--log-file amc.log

User avatar
rednoah
The Source
Posts: 16415
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Docker: "Couldn't watch" No such file or directory.

Post by rednoah » 30 Apr 2019, 03:41

1.
This is a generic Docker question unrelated to FileBot specifically.

My first guess would be any docker settings related to users & permissions might be the cause or the solution when files are moved or copied via the docker volume file system interface:

Code: Select all

-e UMASK=000 \
-e PUID=1000 \
-e PGID=1000 \

2.
FileBot is running inside the docker container, so any file paths you pass in must be valid within the docker container, not within your host:

Code: Select all

docker run -it -v $PWD:/home/d/share/media -v data:/data rednoah/filebot:watcher /home/d/share/media/complete --output /home/d/share/media

3.
Docker solves certain problems. I don't think you have these problems. I recommend using FileBot directly without docker, unless you do have a specific reason for using docker.
:idea: Please read the FAQ and How to Request Help.

n4pl
Posts: 1
Joined: 19 Jul 2019, 10:00

Re: Docker: "Couldn't watch" No such file or directory.

Post by n4pl » 19 Jul 2019, 11:12

@w0wreally

did u find any solution? im at the same point. I have all my used applications in docker but only Filebot everytime writes as root user...

Edit: i got it with

Code: Select all

docker run -d \
--name=filebot \
-v /mnt/media1:/volume1 \
-v /home/n4pl/dockerfiles/filebot:/data \
-p 5452:5452 \
-u $(id -u ${USER}):$(id -g ${USER}) \
--restart always \
rednoah/filebot:node
after first start i have to "chown n4pl: /home/n4pl/dockerfiles/filebot" and restart the container because he creates it as root (but cant write at this point) but then it works... finaly

Second Edit: Okay.. this ends up with an error when u execute filebot

Code: Select all

Permission denied
java.io.IOException: Permission denied
:roll:

Post Reply