4 ms·
> because docker build does not allow you to temporarily mount the cached dependencies. Why do you believe this point is relevant? If you can mount a drive the
by geezerjay 7y ago
> because docker build does not allow you to temporarily mount the cached dependencies.
Why do you believe this point is relevant? If you can mount a drive then you can access its contents on the host, and if you can access files on the host then those contents are also accessible in a Docker build.
- pulse7 7y agoYou CAN NOT mount a drive with "docker build". You CAN however mount a drive with "docker run". So therefore: Dockerfile = docker run + docker commit + MANY unneeded limitations
- geezerjay 7y ago> You CAN NOT mount a drive with "docker build". No one said that. I stated the fact that you can access files from the host during a docker build, thus it's irrelevant if you can mount drives or not. Just copy the files into your build stage and that's it.