Container doesn't start because of an permission error while trying to open /config/log/nginx/error.log
The file doesn't even exist in the folder specified. manually creating the file doesn't fix the problem.
Expected Behavior
container starts without errors.
Steps To Reproduce
I have the config folder for Jdownloader mounted on an NFS Share and when I start up the container it crashes with the permission error.
When I look at the mounted folder the file isn't even there.
I am running this on docker swarm. I temporarily changed the config folder to a local folder on the host and JD starts. Wiredly enough downloading to the NFS Share works without any problems.
But i obviously want the config folder on the NFS Share so any node in the swarm can start up the container while retaining all configuration changes made.
Current Behavior
Container doesn't start because of an permission error while trying to open /config/log/nginx/error.log The file doesn't even exist in the folder specified. manually creating the file doesn't fix the problem.
Expected Behavior
container starts without errors.
Steps To Reproduce
I have the config folder for Jdownloader mounted on an NFS Share and when I start up the container it crashes with the permission error. When I look at the mounted folder the file isn't even there.
Environment
Container creation
services: jdownloader: image: jlesage/jdownloader-2:latest volumes:
example.domain.tld
)example.domain.tld
)volumes: jd_config: driver_opts: type: nfs o: "nfsvers=4,addr=xxx.xxx.xxx.x,rw,nolock" device: ":/volume1/dockerswarm/data/jdownloader" jd_download: driver_opts: type: nfs o: "nfsvers=4,addr=xxx.xxx.xxx.x,rw,nolock" device: ":/volume1/Plex/Downloads" networks: traefik-public: external: true
Container log
Container inspect
Anything else?
I am running this on docker swarm. I temporarily changed the config folder to a local folder on the host and JD starts. Wiredly enough downloading to the NFS Share works without any problems. But i obviously want the config folder on the NFS Share so any node in the swarm can start up the container while retaining all configuration changes made.