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
I'm not 100% sure but I believe the entire context directory is sent to the daemon during a container build (minus any files specified in the dockerignore file).
Currently the default context is the monorepo root, and then COPY statements scope out what to add to the container e.g. COPY dist/apps/my-new-app .
This seems like it would have poor performance if the entire monorepo is copied into the daemon before build. Would it be better to set the context to the dist/apps/my-new-app folder?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm not 100% sure but I believe the entire context directory is sent to the daemon during a container build (minus any files specified in the dockerignore file).
Currently the default context is the monorepo root, and then COPY statements scope out what to add to the container e.g.
COPY dist/apps/my-new-app .
This seems like it would have poor performance if the entire monorepo is copied into the daemon before build. Would it be better to set the context to the
dist/apps/my-new-app
folder?Beta Was this translation helpful? Give feedback.
All reactions