Skip to content
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

using wildcard does not use cache with multistage build #573

Closed
manishtomar opened this issue Aug 15, 2018 · 1 comment · Fixed by #809
Closed

using wildcard does not use cache with multistage build #573

manishtomar opened this issue Aug 15, 2018 · 1 comment · Fixed by #809
Assignees

Comments

@manishtomar
Copy link

manishtomar commented Aug 15, 2018

Steps to reproduce:

  1. Unzip buildkitbug.zip and cd buildkitbug
  2. docker build -t test .
  3. echo anything > conf/sample.yaml
  4. docker build -t test .

Expected results:

Since only conf directory is changed I expect first stage (builder) to be completely cached when run again instead COPY and RUN commands are run. This does not happen if COPY does not use wildcard, i.e.COPY main.go /app instead of COPY *.go /app. This problem does not exist in legacy builder.

@tiborvass tiborvass self-assigned this Aug 15, 2018
@nphmuller
Copy link

This is currently blocking us from using buildkit, because it destroys build performance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants