Closed DaCHack closed 9 months ago
Thank you for reporting this. If you find this product useful, please consider donation to help me continue maintain and create great products ( )
I don't think the issue is related to this image nor to JDownloader but seems to be related to your configuration. Please, have a look at https://forums.docker.com/t/docker-compose-mount-samba-volume/132407/12
I was in fact just me not understanding how Portainer/Docker Manages the volumes.
I already tried to fix it by adding
uid=0,gid=0,forceuid,forcegid,rw
to the mount options and then updating the stack. But I needed to manually remove the old volume first. Now it works.
Output of
docker inspect jdownloader --format='{{index .Config.Labels.version}}'
:Description
SMB share for the downloads directory is mounted ro only and seemly cannot be forced to mount in rw mode.
Command line I used to start the container
Docker compose in Portainer:
Steps to reproduce the issue:
Describe the results you received: MyJDownloader gives "Invalid download directory"
Touch test
in download directory via console givesread-only file system
Describe the results you expected: Directory is writable and downloads are stored there
Additional information you deem important (e.g. issue happens only occasionally):
Provide some logs (
docker logs jdownloader
)docker logs jdownloader
findmnt