New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filebot not found because its in a Docker container #36
Comments
I wish I could say I'm more versed in the intricacies of calling docker processes from other docker processes, so it's quite possible that there's something in there preventing the call that I can't help you with. I see that you change the owner and the permissions on the deluge bin to have the setuid and setgid permissions, but are you sure that deluge is running with root permissions, and that that user has the required permissions to call filebot? In general, if the user in a simple shell can use the Looking closer, I'm pretty sure that the alias you're using won't help the deluged process. As far as I know, You could try substituting your alias with a basic shell script at
Just make sure that the script is chmodded to 755 and that it works like you expect, namely that it passes your arguments to filebot and you get back both the stdout and stderr streams. So long as that works, the plugin should be able to use it too. |
Forgot the last bit. As for the part where filebottool keeps getting disabled after you restart, I'm not sure what could be causing that. I'm pretty sure there's some state file that deluge writes to keep track of what plugins are enabled or dissabled. Maybe that's either not getting saved or can't be read for some reason? I'm not entirely sure but it seems like something from the docker side of things. |
Thanks for the tip on .bashrc, didn't know that. Maybe there are other checks in the plugin that might give this false negative? As for the plugin being disabled issue, sorry, I cannot reproduce it now. UPD: in the meantime I managed to build one container with both apps, it detects Filebot as expected. |
I'm glad you got it working, I'm not sure what could be causing the filebot not found error. |
Hi, thanks for the plugin.
I am getting "Filebot not found", and the plugin turns off in the preferences on each system restart.
I am running my setup on an armv7 NAS, so to avoid dealing with compilation, I run Deluge as a container and Filebot as another container. The
filebot
command in the Deluge container is aliased to runfilebot
in the Filebot container (by binding with host machine's Docker process). So runningfilebot -version
from inside the Deluge container gives a few seconds lag, but other than that there's no difference from running it natively (AFAIK). Now, I'm not sure howfind_executable
works, so I tried to dupe the plugin by appending PATH with a fake path, gave more privileges to deluged — still, my limited knowledge of Linux is insufficient to solve this.Is it possible to make this setup work?
Here's my deluge image:
Docker-compose:
The text was updated successfully, but these errors were encountered: