Adrian-at-CrimsonAzure
commented
3 years ago I came up with a very hacky solution:
version: '3.3'
volumes:
jdownloader:
services:
jdownloader:
image: jaymoulin/jdownloader
volumes:
- /etc/localtime:/etc/localtime:ro
- type: volume
source: jdownloader
target: /opt/JDownloader
volume:
nocopy: false
- /Tank/Media/Downloads/JDownloader:/opt/JDownloader/Downloads
environment:
MYJD_USER: email@email.com
MYJD_PASSWORD: "PASSWORD"
MYJD_DEVICE_NAME: Name
#XDG_DOWNLOAD_DIR: /opt/JDownloader/Downloads
ports:
- 3129:3129
On first creation, the contents of /opt/JDownloader are copied into the volume called jdownloader, making the whole application persistent.
\
\
\
I'm pretty sure the root cause is that Portainer (and any other manager) see JDownloader shutdown and immediately kill the container. This removes the tmp and update directories and everything starts from square one again. The other solution is probably to mount those folders to volumes as well, but this works so unless there's a proper fix (or I'm missing some config option or something) then I'll probably stick with this.
jaymoulin
Output of
docker inspect jdownloader --format='{{index .Config.Labels.version}}':Description
Cannot get JDownloader to actually run, it just continually updates. Either I'm an idiot and missing something, or something is messed up. Using the recommended identify method doesn't help either. This is basically the same as #91 but I have provided logs.
Docker Compose
Steps to reproduce the issue:
Describe the results you received: Runs first time update/setup, restarts container, runs first time update/setup again.
Logs: