Over the years Windows was not the good candidate to work with Docker. But since the release of Docker for Windows, you can work with Docker containers on Windows much easier. However, it's not always an easy piece of cake, and especially when you work with some bash scripts.
One of the hardest problems to solve is when, after running your image, Docker says that:
exec user process caused no such file
At first glance you may think about the absence of the file. But when you check, the file is there. The next step is often the verification of the permissions. When you play around to lower them, you certainly will get a "permission denied" error. So, what's the problem?
In fact, Windows uses different new line character than the Unix systems. When the script is read by a Linux distribution, it doesn't see the instructions on new lines and fails the execution. To fix it, you must replace the Windows new lines by the Unix ones. And the way of doing that will depend of course on your IDE.