Aaron Lehmann 8691a77e44 Fix build cache false positives when build context tar contains unnormalized paths ... 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>		2016-04-14 17:57:45 -07:00
..
dockerfile	builder: replace cancelled channel with net/context	2016-03-25 08:19:29 -07:00
dockerignore	Fix ReadAll to run on Windows.	2016-02-04 14:01:17 -08:00
builder.go	fix typos	2016-03-26 22:06:45 +08:00
context.go	Move getContext… function to builder package	2016-02-11 20:59:59 +01:00
context_unix.go	Move validateContextDirectory to builder package.	2016-02-09 22:19:09 +01:00
context_windows.go	Move validateContextDirectory to builder package.	2016-02-09 22:19:09 +01:00
dockerignore.go	utils: move dockerignore function to builder/dockerignore	2015-12-14 14:59:52 +01:00
git.go	utils: move git functions to pkg/gitutils	2015-12-14 14:59:52 +01:00
remote.go	Move getContext… function to builder package	2016-02-11 20:59:59 +01:00
remote_test.go	remove unnecessary temporary variable	2015-11-26 10:25:55 +08:00
tarsum.go	Fix build cache false positives when build context tar contains unnormalized paths	2016-04-14 17:57:45 -07:00