"Permission denied"/"No such file or directory" when running `sudo docker exec jdownloader configure` about docker-jdownloader

[jaymoulin]

Yep, rights problem. Your cfg directory has write rights for root but you're running your container with your own user. Either change owner of your cfg directory or use a container without the -u XXXX param, but you'll probably have to recreate your container

[jaymoulin]

Looks like you have a permission error on your volume + you seems to use docker with docker rights instead of your own user. What command did you use to create your container?

[amrazi]

I used:

docker run -d --restart=always -v ~/Downloads:/root/Downloads -v ~/jdownloader/cfg:/opt/JDownloader/cfg --name jdownloader -u $(id -u):$(id -g) jaymoulin/jdownloader

[jaymoulin]

with or without sudo ?

Could you check that the rights for ~/jdownloader/cfg matches the user for $(id -u):$(id -g)

[amrazi]

I initially used without sudo, although with it gives the same message.

Running ls -l in ~/jdownloader/cfg returns drwxr-xr-x 2 root root 4096 Jan 28 15:06 cfg

[amrazi]

That was it! Started fresh by removing all containers, running docker run -d --restart=always -v ~/Downloads:/root/Downloads -v ~/jdownloader/cfg:/opt/JDownloader/cfg --name jdownloader -u $(id -u):$(id -g) jaymoulin/jdownloader, and running sudo docker exec jdownloader configure [email protected] password with no error.

However, the JDownloader website does not recognize any running JDownloader2 instances.

[amrazi]

Spoke too soon, the website sees it. Thank you for the help and making this container!

[amrazi]

I am actually working with a reinstall of this on a fresh OS, and I am running into this again, however, taking ownership does not seem to help. What insight does drwxr-xr-x 2 root root 4096 Jan 28 15:06 cfg lend and what user:group should I aim for?

I have used rock64:docker, rock64:rock64, and rock64:root to no avail (where rock64 is my user). I have the docker group created and rock64 is in it.

[jaymoulin]

Your cfg folder is created as root (only user that can write file into it) and you created your container with -u XXX parameter which mean run with user rights.

• Delete your container
• start without -u parameter OR give correct rights permissions to your folders