Improve headless container (e.g. Docker) experience
I recently moved all the services on my download machine into Docker containers. I've found all the solutions (including my own) to containerize JDownloader I've tried so far to be hacky and unreliable, and would like to do better.
I think some documentation about the caveats of running in Docker would help a lot. For instance, which files need to persist and which don't. It doesn't seem like I can turn off auto-updates when running headless, no matter if I set all the settings that sound relevant (most notably autoupdatecheckenabled). Whenever the container restarts and there's a new update, the update will be dowloaded and then the container wants to exit. At this point, the container orchestrator will spawn a new container - but since container filesystems are ephemeral, the downloaded update will be gone. Whereupon, the update process starts again, and we're stuck in a loop.
I'm not sure if this is something you guys want to support, but it would be nice.
|