Open paolomainardi opened 3 years ago
Any feedback on this ? cc @tonistiigi sorry for mentioning you, i saw that you are the more involved one on the other issues.
I'm experiencing the very same, spent an evening already debugging this.
See https://github.com/moby/moby/issues/32816#issuecomment-910030001 There might be issues with different file masks - pipeline clone vs local clone
Scenario: Building with docker-compose native build and inline cache active
Test-case: https://github.com/paolomainardi/buildkit-cache-testcase
Description::
As the title suggests, i'm experiencing inconsistencies while building the very same image on a CI environment and other environments, to be more generic it seems that for some reasons the resulting image can be used as a cache layer just from the generating environment, in this case Github Actions.
As you can see here: https://github.com/paolomainardi/buildkit-cache-testcase/runs/2051488604 The image is built re-using the cache layers previously built and pushed to the docker registry.
This is the executed script:
Problem:
Standing the previous chapter, i would expect to clone this repo, run the very same commands and benefit of cached layers, well of course, that is not the case:
My docker info:
What i am doing or understood wrong here ? Should it supposed to be cached right ?