![]() ![]() "defaultdownloadfolder" : "/root/Downloads", Either by editing it manually/GUI or doing a search and replace in the Dockerfile or entrypoint.sh, etc/ Then just change the ".json" file to point to the new directory. That should only require adding a line to the RUN command in the Dockerfile. Specifically that is has a mode of "700" to only allow the user with uid "0" to read, write or execute under that cd /root/Downloadsīash: cd: /root/Downloads: Permission the image build is changed to create the Downloads directory as /opt/JDownloader/Downloads, there should be no issue. By default no user should have access to root's files so /root/ has pretty restrictive permissions. rw-r-r- 1 jdownloader users 1012515 Feb 17 22:42 sevenzipjbinding1509Linux.jarĭrwxr-xr-x 3 jdownloader users 4096 Apr 5 05:15 themesĭrwxr-xr-x 7 jdownloader users 4096 Apr 5 05:38 tmpĭrwxr-xr-x 3 jdownloader users 4096 Apr 5 05:15 toolsĭrwxr-xr-x 5 jdownloader users 4096 Apr 5 05:15 translationsĭrwxr-xr-x 4 jdownloader users 4096 Apr 5 05:15 problem lies in the fact that the "Downloads" directory lives at /root/Downloads/ which in itself has the proper permissions on it. rw-r-r- 1 jdownloader users 72390 Feb 17 22:42 sevenzipjbinding1509.jar rw-r-r- 1 jdownloader users 39624 Apr 5 05:15 license_german.txtĭrwxr-xr-x 5 jdownloader users 4096 Apr 5 05:15 licensesĭrwxr-xr-x 13 jdownloader users 4096 Apr 5 05:38 logs ![]() rw-r-r- 1 jdownloader users 32034 Apr 5 05:15 license.txt rwxr-xr-x 1 jdownloader users 668 Feb 17 22:42 entrypoint.shĭrwxr-xr-x 2 jdownloader users 4096 Apr 5 05:38 extensionsĭrwxr-xr-x 2 jdownloader users 4096 Apr 5 05:15 javaĭrwxr-xr-x 4 jdownloader users 4096 Apr 5 05:15 jdĭrwxr-xr-x 8 jdownloader users 4096 Apr 5 05:15 libs rw-r-r- 1 jdownloader users 320 Apr 5 05:15 build.jsonĭrwxr-xr-x 4 jdownloader users 28672 Apr 5 05:38 cfg ![]() rw-r-r- 1 jdownloader users 5 Apr 5 05:38 JDownloader.pid rw-r-r- 1 jdownloader users 3640229 Apr 5 05:15 JDownloader.jar rw-r-r- 1 jdownloader users 4 Apr 5 05:38 JD2.port rw-r-r- 1 jdownloader users 0 Apr 5 05:38 JD2.lock It's just weird because I blamed the jdownloader code and it has been unmodified for like 5 years while this docker code was initially checked in 2.5 years ago, so theoretically using the bare /media shouldn't have worked from day 1 at all.Drwxr-xr-x 24 jdownloader users 4096 Apr 5 05:38. Basically, the code does expects /media to be followed by something, otherwise as I saw from the logs it is possible that the filename will be erroneously included and treated as the folder, which does not match the needed existence check.īecause I believe the purpose of that /media is the Docker container is different from that in typical Linux systems anyway, eventually I decided to simply change the default download directory to something entirely different (I mounted on /jdownloader/Downloads instead), and that essentially skipped all the checks here and it worked for me. I entered the container and dug through the logs and from web search of the log message I bumped into the JDownloader source file which should explain that. ![]()
0 Comments
Leave a Reply. |