-
Notifications
You must be signed in to change notification settings - Fork 2
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
Use registry for cache #4
Comments
OK, I have what I think is bad news. Although the issues aren't perfectly clear, I believe that the Harbor registry does not recognize the format of the build cache. goharbor/harbor#14774 This may be true of other registries as well:
The evidence here is from running
with a minimal docker-compose file, where
Unsurprisingly, we see
but then at the end we see
which matches goharbor/harbor#14774. |
opencontainers/image-spec#870 has
|
I believe #8 finally obviates the need for this kind of caching. |
Under correction from @rebeccacremona I am reopening this; #8 solves our problem of building and pushing an image too frequently, but does not accomplish the caching of the layers that make up the image. For future reference, a Harbor update might allow us to use a cache manifest, or we might switch to another registry. |
750f46aa actually solves the problem of building and pushing too frequently; |
These cache flags are wrong:
The way it wants to work is to cache-from the registry (in all cases), and cache-to the registry (if logged into the registry).
The text was updated successfully, but these errors were encountered: