jdownloader2 on docker

thedogg · 15. April 2022

Hello,

I am having the problem to get into my jdownloader2 installed on docker through the web:port. I simply follow the code below and it works fine (of course I adjusted the patch etc.) but at the end even if it is running I can't get into it using the port 5800. Do I need to do something else in this code? I have read that the login details may be necessary but I want to avoid it and use it just within my internal network.

I've triad also to do it more manually in containers with setting up all of the env parameters and variables but effect is exactly the same. I added PUID and PGID as well as selected host as the environment.

Is there maybe anything I have overlooked and small detail?

Code

version: '3'
services:
  jdownloader-2:
    image: jlesage/jdownloader-2
    ports:
      - "5800:5800"
    volumes:
      - "/docker/appdata/jdownloader-2:/config:rw"
      - "$HOME/Downloads:/output:rw"

Agricola · 15. April 2022

The code you provided is the example listed on GitHub. What are the ACTUAL paths you used for config and output?

thedogg · 15. April 2022

I have simply used the code below

Code

version: '3'
services:
  jdownloader-2:
    image: jlesage/jdownloader-2
    ports:
      - "5800:5800"
    volumes:
        - /var/lib/docker/volumes/jdownloader-2:/config:rw
        - /srv/dev-disk-by-uuid-e69265f5-6a57-4ecd-b6e4-3cbf087d82bf/pi_2TB/Downloads - jdownloader/Downloaded:/output:rw

gderf · 15. April 2022

I suggest not using blank spaces in paths.

What is in the container log?

thedogg · 15. April 2022

Zitat von gderf

I suggest not using blank spaces in paths.

What is in the container log?

I have not defined it. It is entire code I have used.

It does not start automatically and stops after a few seconds.

In log I can see:

Code

 -1 }">standard_init_linux.go:228: exec user process caused: exec format error
 -1 }">standard_init_linux.go:228: exec user process caused: exec format error
 -1 }">standard_init_linux.go:228: exec user process caused: exec format error

Wolf2000 · 15. April 2022

- /srv/dev-disk-by-uuid-e69265f5-6a57-4ecd-b6e4-3cbf087d82bf/pi_2TB/Downloads-jdownloader/Downloaded:/output:rw

change this

Soma · 15. April 2022

Zitat von thedogg
I have not defined it. It is entire code I have used.

It does not start automatically and stops after a few seconds.
In log I can see:
Code
 -1 }">standard_init_linux.go:228: exec user process caused: exec format error
 -1 }">standard_init_linux.go:228: exec user process caused: exec format error
 -1 }">standard_init_linux.go:228: exec user process caused: exec format error

On what hardware are you running this?

The container tag only runs on amd64.

That error means you're trying to run it on a different architecture.

Wolf2000 · 15. April 2022

It doesn't work if I installed it but thedogg wrote it wrong

jaymoulin/jdownloader - Docker Image | Docker Hub

this should work

thedogg · 15. April 2022

Zitat von Soma

On what hardware are you running this?
The container tag only runs on amd64.

That error means you're trying to run it on a different architecture.

Yes I have just found out it, sorry bit docker is a totally new thing for me and I have not noticed it. I am using raspberry pi 4

I have installed now jaymoulin/jdownloader but I am not sure if it is exactly the same because it is running but I can't open jdownloader in web.

Wolf2000 · 15. April 2022

antlafarge/jdownloader - Docker-Image-| Docker-Hub

look at that

thedogg · 15. April 2022

Zitat von Wolf2000

antlafarge/jdownloader - Docker-Image-| Docker-Hub

look at that

I have seen it, but I think it works different way. I can use myjdownloader account here. It is not like a app opened in web.

Agricola · 16. April 2022

Code

version: '3'
services:
  jdownloader-2:
    image: jlesage/jdownloader-2
    container_name: jdownloader2
    network_mode: pwh
    ports:
      - "5800:5800"
    volumes:
      - /sym/appdata/jdownloader2:/configure:rw
      - /sym/data/downloads:/output:rw
    restart: unless-stopped

Alles anzeigen

I just deployed this and it worked like a charm on an amd64 machine. thedogg your download path on line nine is not right. There should not be any spaces. Also, you should not have your docker path set to /var/lib. That is one of the first things before starting any containers: move your docker path away from your system drive. This is done in the OMV GUI under OMV-Extras/Docker. I have mine set to /srv/dev-disk-by-uuid-f8814ed9-9a5c-4e1c-8830-426968c20ea3/appdata/docker Even though you need to change to a different container, you still need to fix these lines and your docker path. Hope you get it going.

Zoki · 16. April 2022

and you should never use the Docker root volumes directory for bind mounts in the container. The volumes directory is where Docker manages its own volumes and volume metadata.

Jetzt mitmachen!