You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
When building with the docker command and the BUILDKIT_INLINE_CACHE=1 build-arg together with the cache-from option, is caching also the multistage intermediate images. This allows to avoid a full build even if the builder compute doesn't have the image locally (the cache-from option alone will trigger also the full build), avoiding also to create a new image in the remote repository every time.
In the module I don't know if it's ignoring the cache-from option or the build-arg option, but it's not using the cache and is performing a full build. This only happens when the image does not exists locally (for example after a docker image prune -a). I suppose that the cache-from option is working fine, so I think that maybe the problem is the lack of buildkit support or something similar.
Community Note
Description
When building with the docker command and the BUILDKIT_INLINE_CACHE=1 build-arg together with the cache-from option, is caching also the multistage intermediate images. This allows to avoid a full build even if the builder compute doesn't have the image locally (the cache-from option alone will trigger also the full build), avoiding also to create a new image in the remote repository every time.
In the module I don't know if it's ignoring the cache-from option or the build-arg option, but it's not using the cache and is performing a full build. This only happens when the image does not exists locally (for example after a
docker image prune -a
). I suppose that the cache-from option is working fine, so I think that maybe the problem is the lack of buildkit support or something similar.New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: