-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ADDing files that may be missing #735
Comments
Thanks for the report. Need to make sure On the other hand, you are right that this is discouraged and undocumented behavior. It might be even considered a bug of the old implementation. Eg. if you compare it to regular |
Also, note that you can use |
yeah just stumbled upon that doc. thanks a lot once again I fully understand that this may not be the intended behaviour. In such case maybe it'd be enough to just add a line to the doc |
also I think it's the |
I have files on host that may not always be present on build time, e.g. caches. Those are
tar
'ed for performance, that's why I use a separate ADD argumentI know that such technique is generally discouraged as one that may produce non-deterministic builds but this is still doable with docker
ADD . caches* ./
this way in case
caches.tar
is present on host - its content gets untarred and placed into the image. If it's not present - nothing bad happenswhen using buildkit i'm getting
#19 75.18 panic: failed to copy /src-1/caches* to app/: no matches found: /src-1/caches*
The text was updated successfully, but these errors were encountered: