The above dockerfile is probably accurate. As you can see there is some stuff going on in the backend when this container is built, so it's not a complete picture of what is going on, but it gets the gist of the thing across I think. Note that I'm pretty new to docker, so there's some things in there that probably don't make sense.
The errors I'm getting are really just
/bin/sh: can't open '...'. However, replacing CMD with something basic, like
ls doesn't fix that issue. However, having done a little testing, setting
ENTRYPOINT doesn't have any effect, just changes the name the
sh binary uses to report errors...