You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi thanks for this wonderful assignment! Docker tarballs and sends everything in the working directory to its Docker daemon. Thus, if one has written some code and compiled (thus lots of intermediate files) and trigger docker build, then he will accidentally tarballs all of the intermediate files (which can be large) and send to daemon, which can take some additional time.
Solution: For example, create a subfolder named image and put Dockerfile to image/Dockerfile. Then trigger docker build there, and almost nothing will need to be tarballed.
Just a tiny suggestion, of course not a big problem :)
The text was updated successfully, but these errors were encountered:
Hi thanks for this wonderful assignment! Docker tarballs and sends everything in the working directory to its Docker daemon. Thus, if one has written some code and compiled (thus lots of intermediate files) and trigger
docker build
, then he will accidentally tarballs all of the intermediate files (which can be large) and send to daemon, which can take some additional time.Solution: For example, create a subfolder named
image
and put Dockerfile toimage/Dockerfile
. Then triggerdocker build
there, and almost nothing will need to be tarballed.Just a tiny suggestion, of course not a big problem :)
The text was updated successfully, but these errors were encountered: