-
Notifications
You must be signed in to change notification settings - Fork 62
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
Current cache-from configuration format doesn't allow for cache types #194
Comments
The cache_from here is designed to work directly with type=registry, which is the default, so you would only need to specify the registry not the type, for example |
Gotcha, yeah we're using registry caches, but this still prevents using other parameters like We resolved our issues by inlining our docker build instead, since we didn't want to rely layers of updates and abstractions, but if this arg is going to be useful, I think adhering to standard syntax is a must. (Or, the limitations should be documented) |
Orb version
Current
What happened
When using
cache-from: type=registry,ref=<registry>/<repo>:<tag>
, I seeand essentially no caching behavior is observed.
Expected behavior
The entire argument should be taken as a single cache-from argument, instead of being split on the comma with
each part assumed to be a different cache source. I'd suggest accepting a list. This behavior is extremely unexpected
while trying to use this orb, and is a sufficient enough blocker to not use it at all.
Am I missing anything with how to use this config? I read through the code as well.
The text was updated successfully, but these errors were encountered: