On your host, enter your credentials (in quotes) to the file .MyJDownloaderSettings.GNU GPLv3 (but partly closed-source) Stop the container: docker stop jdownloader (or with the OMV GUI)ģ. Launch with these settings and wait a minute for the container to initialize.Ģ. When you are on myjdowloder and you whant to configure download path, it MUST be /downloads (container path).ġ.

When you remove your container, data are preserved and still accessible in host path. It's the directory where I previously created jdownloader folder. In my case, to access to my downloads, i go to /srv/dev-disk-by-label-DATA/jdownloader/Downloads (host path) in my OMV system. Now, create a directory called 'jdownloader' where you want to store your downloads and conf with subfolders 'config' and 'Downloads' (for me it's /srv/dev-disk-by-label-DATA/jdownloader/): You can add the UID and GID of the user you are using for docker. You can access your headless jdownloader running in docker from My. Once created, your container can be started at boot if you want. With docker plugin in OMV, you can pull and run images from GUI.

When you remove container, you remove /config in the container dir but your data are still here because you map it on your host in omvhost/srv/your_disk/jdownloader/config. For exemple, you can map omvhost/srv/your_disk/jdownloader/config to /config directory in the container.

However, when you delete a container, you lost all datas on it so docker created volumes and bind mounts. This container is often a 'tiny linux install' and your application is running on it. When you run ('launch') an image it launches your app in a container.

When you install docker on omv, you have to search here for docker images of applications you are looking for (jdownloader here) and choose an image to run. I advise you to use docker when possible (instead of omv plugins) so your omv install stay clear and it is easier to update/upgrade applications and system.

Jdownloader plugin chrome