Shell
Need help with docker-jdownloader-2?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.
jlesage

Description

Docker container for JDownloader 2

150 Stars 34 Forks 139 Commits 32 Opened issues

Services available

Need anything else?

Docker container for JDownloader 2

Docker Image Size Build Status GitHub Release Donate

This is a Docker container for JDownloader 2.

The GUI of the application is accessed through a modern web browser (no installation or configuration needed on the client side) or via any VNC client.


JDownloader 2 logoJDownloader 2

JDownloader 2 is a free, open-source download management tool with a huge community of developers that makes downloading as easy and fast as it should be. Users can start, stop or pause downloads, set bandwith limitations, auto-extract archives and much more. It's an easy-to-extend framework that can save hours of your valuable time every day!


Table of Content

Quick Start

NOTE: The Docker command provided in this quick start is given as an example and parameters should be adjusted to your need.

Launch the JDownloader 2 docker container with the following command:

docker run -d \
    --name=jdownloader-2 \
    -p 5800:5800 \
    -v /docker/appdata/jdownloader-2:/config:rw \
    -v $HOME/Downloads:/output:rw \
    jlesage/jdownloader-2

Where: -

/docker/appdata/jdownloader-2
: This is where the application stores its configuration, log and any files needing persistency. -
$HOME/Downloads
: This is where downloaded files are stored.

Browse to

http://your-host-ip:5800
to access the JDownloader 2 GUI.

Usage

docker run [-d] \
    --name=jdownloader-2 \
    [-e =]... \
    [-v :[:PERMISSIONS]]... \
    [-p :]... \
    jlesage/jdownloader-2

| Parameter | Description | |-----------|-------------| | -d | Run the container in the background. If not set, the container runs in the foreground. | | -e | Pass an environment variable to the container. See the Environment Variables section for more details. | | -v | Set a volume mapping (allows to share a folder/file between the host and the container). See the Data Volumes section for more details. | | -p | Set a network port mapping (exposes an internal container port to the host). See the Ports section for more details. |

Environment Variables

To customize some properties of the container, the following environment variables can be passed via the

-e
parameter (one for each variable). Value of this parameter has the format
=
.

| Variable | Description | Default | |----------------|----------------------------------------------|---------| |

USER_ID
| ID of the user the application runs as. See User/Group IDs to better understand when this should be set. |
1000
| |
GROUP_ID
| ID of the group the application runs as. See User/Group IDs to better understand when this should be set. |
1000
| |
SUP_GROUP_IDS
| Comma-separated list of supplementary group IDs of the application. | (unset) | |
UMASK
| Mask that controls how file permissions are set for newly created files. The value of the mask is in octal notation. By default, this variable is not set and the default umask of
022
is used, meaning that newly created files are readable by everyone, but only writable by the owner. See the following online umask calculator: http://wintelguy.com/umask-calc.pl | (unset) | |
TZ
| TimeZone of the container. Timezone can also be set by mapping
/etc/localtime
between the host and the container. |
Etc/UTC
| |
KEEP_APP_RUNNING
| When set to
1
, the application will be automatically restarted if it crashes or if a user quits it. |
0
| |
APP_NICENESS
| Priority at which the application should run. A niceness value of -20 is the highest priority and 19 is the lowest priority. By default, niceness is not set, meaning that the default niceness of 0 is used. NOTE: A negative niceness (priority increase) requires additional permissions. In this case, the container should be run with the docker option
--cap-add=SYS_NICE
. | (unset) | |
CLEAN_TMP_DIR
| When set to
1
, all files in the
/tmp
directory are deleted during the container startup. |
1
| |
DISPLAY_WIDTH
| Width (in pixels) of the application's window. |
1280
| |
DISPLAY_HEIGHT
| Height (in pixels) of the application's window. |
768
| |
SECURE_CONNECTION
| When set to
1
, an encrypted connection is used to access the application's GUI (either via a web browser or VNC client). See the Security section for more details. |
0
| |
VNC_PASSWORD
| Password needed to connect to the application's GUI. See the VNC Password section for more details. | (unset) | |
X11VNC_EXTRA_OPTS
| Extra options to pass to the x11vnc server running in the Docker container. WARNING: For advanced users. Do not use unless you know what you are doing. | (unset) | |
ENABLE_CJK_FONT
| When set to
1
, open-source computer font
WenQuanYi Zen Hei
is installed. This font contains a large range of Chinese/Japanese/Korean characters. |
0
| |
INSTALL_EXTRA_PKGS
| Space-separated list of Alpine Linux packages to install. See https://pkgs.alpinelinux.org/packages?name=&branch=v3.9&arch=x86_64 for the list of available Alpine Linux packages. | (unset) |

Data Volumes

The following table describes data volumes used by the container. The mappings are set via the

-v
parameter. Each mapping is specified with the following format:
:[:PERMISSIONS]
.

| Container path | Permissions | Description | |-----------------|-------------|-------------| |

/config
| rw | This is where the application stores its configuration, log and any files needing persistency. | |
/output
| rw | This is where downloaded files are stored. |

Ports

Here is the list of ports used by the container. They can be mapped to the host via the

-p
parameter (one per port mapping). Each mapping is defined in the following format:
:
. The port number inside the container cannot be changed, but you are free to use any port on the host side.

| Port | Mapping to host | Description | |------|-----------------|-------------| | 5800 | Mandatory | Port used to access the application's GUI via the web interface. | | 5900 | Optional | Port used to access the application's GUI via the VNC protocol. Optional if no VNC client is used. | | 3129 | Optional | Port used by MyJDownloader mobile applications and browser extensions to establish a direct connect to the JDownloader Docker container instance. Port needs to be exposed only if MyJDownloader is enabled and configured in Direct Connection mode. NOTE: Since this port is being reported to the MyJDownloader online service, the port mapped on the host side must be the same (i.e. 3129). |

Changing Parameters of a Running Container

As seen, environment variables, volume mappings and port mappings are specified while creating the container.

The following steps describe the method used to add, remove or update parameter(s) of an existing container. The generic idea is to destroy and re-create the container:

  1. Stop the container (if it is running):
    docker stop jdownloader-2
    
  2. Remove the container:
    docker rm jdownloader-2
    
  3. Create/start the container using the
    docker run
    command, by adjusting parameters as needed.

NOTE: Since all application's data is saved under the

/config
container folder, destroying and re-creating a container is not a problem: nothing is lost and the application comes back with the same state (as long as the mapping of the
/config
folder remains the same).

Docker Compose File

Here is an example of a

docker-compose.yml
file that can be used with Docker Compose.

Make sure to adjust according to your needs. Note that only mandatory network ports are part of the example.

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

Docker Image Update

If the system on which the container runs doesn't provide a way to easily update the Docker image, the following steps can be followed:

  1. Fetch the latest image:
    docker pull jlesage/jdownloader-2
    
  2. Stop the container:
    docker stop jdownloader-2
    
  3. Remove the container:
    docker rm jdownloader-2
    
  4. Start the container using the
    docker run
    command.

Synology

For owners of a Synology NAS, the following steps can be used to update a container image.

  1. Open the Docker application.
  2. Click on Registry in the left pane.
  3. In the search bar, type the name of the container (
    jlesage/jdownloader-2
    ).
  4. Select the image, click Download and then choose the
    latest
    tag.
  5. Wait for the download to complete. A notification will appear once done.
  6. Click on Container in the left pane.
  7. Select your JDownloader 2 container.
  8. Stop it by clicking Action->Stop.
  9. Clear the container by clicking Action->Clear. This removes the container while keeping its configuration.
  10. Start the container again by clicking Action->Start. NOTE: The container may temporarily disappear from the list while it is re-created.

unRAID

For unRAID, a container image can be updated by following these steps:

  1. Select the Docker tab.
  2. Click the Check for Updates button at the bottom of the page.
  3. Click the update ready link of the container to be updated.

User/Group IDs

When using data volumes (

-v
flags), permissions issues can occur between the host and the container. For example, the user within the container may not exists on the host. This could prevent the host from properly accessing files and folders on the shared volume.

To avoid any problem, you can specify the user the application should run as.

This is done by passing the user ID and group ID to the container via the

USER_ID
and
GROUP_ID
environment variables.

To find the right IDs to use, issue the following command on the host, with the user owning the data volume on the host:

id 

Which gives an output like this one:

uid=1000(myuser) gid=1000(myuser) groups=1000(myuser),4(adm),24(cdrom),27(sudo),46(plugdev),113(lpadmin)

The value of

uid
(user ID) and
gid
(group ID) are the ones that you should be given the container.

Accessing the GUI

Assuming that container's ports are mapped to the same host's ports, the graphical interface of the application can be accessed via:

  • A web browser:

    http://:5800
    
  • Any VNC client:

    :5900
    

Security

By default, access to the application's GUI is done over an unencrypted connection (HTTP or VNC).

Secure connection can be enabled via the

SECURE_CONNECTION
environment variable. See the Environment Variables section for more details on how to set an environment variable.

When enabled, application's GUI is performed over an HTTPs connection when accessed with a browser. All HTTP accesses are automatically redirected to HTTPs.

When using a VNC client, the VNC connection is performed over SSL. Note that few VNC clients support this method. SSVNC is one of them.

SSVNC

SSVNC is a VNC viewer that adds encryption security to VNC connections.

While the Linux version of SSVNC works well, the Windows version has some issues. At the time of writing, the latest version

1.0.30
is not functional, as a connection fails with the following error:
ReadExact: Socket error while reading
However, for your convenience, an unofficial and working version is provided here:

https://github.com/jlesage/docker-baseimage-gui/raw/master/tools/ssvncwindowsonly-1.0.30-r1.zip

The only difference with the official package is that the bundled version of

stunnel
has been upgraded to version
5.49
, which fixes the connection problems.

Certificates

Here are the certificate files needed by the container. By default, when they are missing, self-signed certificates are generated and used. All files have PEM encoded, x509 certificates.

| Container Path | Purpose | Content | |---------------------------------|----------------------------|---------| |

/config/certs/vnc-server.pem
|VNC connection encryption. |VNC server's private key and certificate, bundled with any root and intermediate certificates.| |
/config/certs/web-privkey.pem
|HTTPs connection encryption.|Web server's private key.| |
/config/certs/web-fullchain.pem
|HTTPs connection encryption.|Web server's certificate, bundled with any root and intermediate certificates.|

NOTE: To prevent any certificate validity warnings/errors from the browser or VNC client, make sure to supply your own valid certificates.

NOTE: Certificate files are monitored and relevant daemons are automatically restarted when changes are detected.

VNC Password

To restrict access to your application, a password can be specified. This can be done via two methods: * By using the

VNC_PASSWORD
environment variable. * By creating a
.vncpass_clear
file at the root of the
/config
volume. This file should contain the password in clear-text. During the container startup, content of the file is obfuscated and moved to
.vncpass
.

The level of security provided by the VNC password depends on two things: * The type of communication channel (encrypted/unencrypted). * How secure the access to the host is.

When using a VNC password, it is highly desirable to enable the secure connection to prevent sending the password in clear over an unencrypted channel.

ATTENTION: Password is limited to 8 characters. This limitation comes from the Remote Framebuffer Protocol RFC (see section 7.2.2). Any characters beyond the limit are ignored.

Reverse Proxy

The following sections contain NGINX configurations that need to be added in order to reverse proxy to this container.

A reverse proxy server can route HTTP requests based on the hostname or the URL path.

Routing Based on Hostname

In this scenario, each hostname is routed to a different application/container.

For example, let's say the reverse proxy server is running on the same machine as this container. The server would proxy all HTTP requests sent to

jdownloader-2.domain.tld
to the container at
127.0.0.1:5800
.

Here are the relevant configuration elements that would be added to the NGINX configuration:

map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

upstream docker-jdownloader-2 { # If the reverse proxy server is not running on the same machine as the # Docker container, use the IP of the Docker host here. # Make sure to adjust the port according to how port 5800 of the # container has been mapped on the host. server 127.0.0.1:5800; }

server { [...]

server_name jdownloader-2.domain.tld;

location / {
        proxy_pass http://docker-jdownloader-2;
}

location /websockify {
    proxy_pass http://docker-jdownloader-2;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $connection_upgrade;
    proxy_read_timeout 86400;
}

}

Routing Based on URL Path

In this scenario, the hostname is the same, but different URL paths are used to route to different applications/containers.

For example, let's say the reverse proxy server is running on the same machine as this container. The server would proxy all HTTP requests for

server.domain.tld/jdownloader-2
to the container at
127.0.0.1:5800
.

Here are the relevant configuration elements that would be added to the NGINX configuration:

map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}

upstream docker-jdownloader-2 { # If the reverse proxy server is not running on the same machine as the # Docker container, use the IP of the Docker host here. # Make sure to adjust the port according to how port 5800 of the # container has been mapped on the host. server 127.0.0.1:5800; }

server { [...]

location = /jdownloader-2 {return 301 $scheme://$http_host/jdownloader-2/;}
location /jdownloader-2/ {
    proxy_pass http://docker-jdownloader-2/;
    location /jdownloader-2/websockify {
        proxy_pass http://docker-jdownloader-2/websockify/;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $connection_upgrade;
        proxy_read_timeout 86400;
    }
}

}

Shell Access

To get shell access to a the running container, execute the following command:

docker exec -ti CONTAINER sh

Where

CONTAINER
is the ID or the name of the container used during its creation (e.g.
crashplan-pro
).

MyJDownloader

MyJDownloader is an online service providing remote access to your JDownloader with Web Interface, Android App, iPhone App, Windows Phone App and Browser Extensions. It allows to check download status, add links and solve captchas from everywhere.

To activate, open the JDownloader UI and click the My.JDownloader tab.

Direct Connection

When using MyJDownloader from a device on the same local network as the JDownloader Docker container instance, Direct Connection mode can be enabled to reduce the latency and increase the bandwidth. With this mode, instead of going through the cloud, the communication is done through a direct connection between the device and JDownloader.

The default container's network being in bridge mode, the Direct Connection mode is not automatically detected/activated and the following steps are required:

  • Make sure the container's port
    3129
    is mapped to the host port
    3129
    . This is done by adding the parameter
    -p 3129:3129
    to the
    docker run
    command.
  • Open the JDownloader UI.
  • Go to Settings->Advanced Settings.
  • Search for
    MyJDownloaderSettings
    .
  • Set
    Custom Device IPs
    to the IP address of the host running the container, between double quotes (e.g.
    "192.168.1.1"
    ).
  • Change the
    Direct Connection Mode
    to
    Allow lan/wan connections with
    manual port forwarding
    .
  • Restart JDownloader (File->Restart).

Click'n'Load

The easiest way to use the Click'n'Load feature is by installing the MyJDownloader browser extension. With this method, the browser extension handles POST requests to

http://127.0.0.1:9666
and forward the links to JDownloader via the MyJDownloader service.

Support or Contact

Having troubles with the container or have questions? Please create a new issue.

For other great Dockerized applications, see https://jlesage.github.io/docker-apps.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.