f2ef2b385c
Issues #2241 #1678 both point to cases where renames can point to incorrect images being used with caching. This commit adds the path of the file (relative to the build context to the hash). A different approach would be to change the underlying function in CacheHasher to include the name (and maybe file size), this was avoided for two reasons: 1. It was unclear whether this would change or break the computed digests outside the context of caching. 2. The CacheHasher does not know the prefix to strip in the filename to compute the hash. |
||
|---|---|---|
| .. | ||
| buildcontext | ||
| cache | ||
| commands | ||
| config | ||
| constants | ||
| creds | ||
| dockerfile | ||
| executor | ||
| fakes | ||
| filesystem | ||
| image | ||
| logging | ||
| mocks/go-containerregistry/mockv1 | ||
| snapshot | ||
| timing | ||
| util | ||
| version | ||