-
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
cache exporting / importing not working as expected - or just not working #723
Comments
The first part of this is fixed with #730 (or just use 0.3.1). I need to validate if the rest of it now works as well or if there is another issue. |
Sorry for a delayed response. You can find the fork of your gist (with modifications) in https://gist.github.com/tonistiigi/1ba21a5bae3b9fd895b28589e57175e9 . All outputs seem correct there to me now. Two issues with the old one:
After these changes everything seemed ok to me. Depending on the version of buildkit you use, you might notice a mismatch of the copy helper image when using |
Thanks @tonistiigi looks great, will take a look shortly. To confirm though, docker still doesn't have the ability to export an image that is compatible with |
Correct |
Just tested out v0.3.3 working perfectly. Thanks alot @tonistiigi |
@tonistiigi Is there an open issue tracking this? It's surprising that |
@tonistiigi @AkihiroSuda this is so confusing. If we can't use |
Or if this depends on what the image has been built with, there should be an error when trying to use an incompatible image. Otherwise how would the user make a difference between a format error or a simple cache miss? |
19.03 supports --import-cache |
Is there a different argument I should be using? |
Sorry I meant --cache-from |
Can you give a example code of how to use |
Because
--cache-from
does not yet work in docker I figured I would have a go at using buildkit directly.I am trying to setup CI/CD infrastructure that will use buildkit in a distributed fashion, across many hosts.
I note there are a few issues tagged with distributed, these are somewhat over my head at the moment, perhaps there is something in these that I have missed, my apologies if so.
Here is an example case: https://gist.github.com/brad-jones/536064fcc180b62be6febfd2fa843024
I feel like I am having similar frustrations to #699 but in my case I am using the Docker Registry and not ECR.
The text was updated successfully, but these errors were encountered: