![]() If a build context tar has path names of the form 'x/./y', they will be stored in this unnormalized form internally by tarsum. When the builder walks the untarred directory tree and queries hashes for each relative path, it will query paths of the form 'x/y', and they will not be found. To correct this, have tarsum normalize path names by calling Clean. Add a test to detect this caching false positive. Fixes #21715 Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com> |
||
---|---|---|
.. | ||
testdata | ||
builder_context.go | ||
builder_context_test.go | ||
fileinfosums.go | ||
fileinfosums_test.go | ||
tarsum.go | ||
tarsum_spec.md | ||
tarsum_test.go | ||
versioning.go | ||
versioning_test.go | ||
writercloser.go |