Aloys Baillet

Thanks again Tonis! I'm was assuming that multiple `RUN --mount=type=cache,target=/tmp/ccache` commands in a given Dockerfile would not share the actual same `/tmp/ccache` folder, but your answer seems to indicate that...

Thanks Fernando! That's great info, and I updated my test repo with all the useful knowledge gathered here. With all this I believe I have enough to really benefit from...

So I went back to my test project and tried to use both instruction cache and mounted cache as fallback, but I can't find a way to use these both...

Indeed, I'm actually maintaining a set of docker images that get built on Azure Pipelines (which has caching available in preview, I believe caching is coming across to GitHub actions...

After some introspection into the buildx container I found this hack that properly moves the whole buildkit cache between nodes: backup: ```bash docker buildx create --name cacheable --use docker buildx...

Unfortunately `--cache-to` does not save the mounted cache to disk, that's the main reason I opened this issue...

Thanks Tonis, I don't think this `from=basestage` helps as I can't find any official way to inject this cache data into any build stage without invalidating the instruction cache. The...

But this means that one has to choose in advance between "mounted cache" and "instruction cache" and it is impossible to know in advance which one will be valid. I...

Thanks Blazej! I'll have a look at these, I'm surprised the build succeeded with those bad symlinks!

It looks like nose2 is correctly discovering tests within the "mongoengine/tests" folder, and then trying to load the document.indexes module, which in turn is trying to import nose1's skip plugin,...