Unable to stop the container about docker-jdownloader-2

[jlesage]

Do you have the same issue if you don't map any volume?

[martinhpunkt]

Hi,

similar problem, but on my side the container stops immediately. The issue does NOT appear when I don't map a volume.

My setup is a little bit different though: FreeNAS 11.3 with Rancher and an nfs mounted volume to the Rancher host to provide persistant volumes from the NAS.

Which leads me to the question if this could be related to permissions. The folders /config and /output are being created.

Any help appreciated!

KR

[jlesage]

If you don't have issue when you don't map a volume, then it is probably related to permissions. Did you adjusted USER_ID and GROUP_ID variables?
Also, using NFS adds another level of permissions. Make sure to verify this part...

[ggogel]

Yes this issue only appears when mounting a volume. I have local paths and smb shares provided by auto-fs mounted to the container. Like I described, the issue also occurs with local paths only. I've running several other containers, which have mounted volumes in the exact same manner without issues on stopping. I'd reckon that JDownloader doesn't give up the lock on a certain file and therefore the container can't unmount the volumes.

I haven't set the USER_ID or GROUP_ID parameter, but I also don't have any permission issues when accessing the files. As long as the container keeps running everything is fine.

[jlesage]

Problem should not longer be relevant with the latest image, since S6 is not used.