Unrar: Input/output error about docker-nzbget

[thelamer]

There are many reasons this might happen just from an application standpoint.

But considering you are running windows I would start by changing the "Security => Umask" value to:

000

[iDVB]

I'd love to know about other options to try. setting the Unmask didn't seem to change the issue.
However, before the unmask change I did notice that I am unable to manipulate (permissions) those files from across my network. Only the Host machine seems to have access to them now.

[thelamer]

From an application standpoint that is it, you are setting the most permissive file permissions possible.

I do not want to discourage you, but Docker for Windows in it's current state kind of sucks. You have to understand you are running software designed around Linux file ownership and permissions and trying to translate that into a world it is not compatible with.

There are hacky work-arounds using bindfs in some containers people really want to work in windows, but I do not think there are any plans from the LS team to officially support windows as a Docker environment.

I know it is extreme, but if this machine is being used as a server and not a daily driver desktop, you might want to seriously consider using Linux if you really want to use Docker for your application stack. This is not the last issue you are going to run into trying to get Docker applications working in WIndows.

[sparklyballs]

this would be appear to be a docker in windows specific issue relating to permissions somehow

closing this

[PenTagaris]

In case someone else finds this thread while researching:

I experienced this while running nzbget on Docker for Windows with my unpack destination on an external drive. The error from unrar within the docker container was Cannot close file.

This seems to be due to write caching being disabled by default for external drives. Selecting "Better Performance" under the drive properties fixed the problem for me.