Ian Campbell 720d8327e2 Push setting of default PATH down into the executor(s) ... Setting the default `PATH` in the `llb.State` on the client side means it depends on the `GOOS` of the buildkit client, rather than of the environment where it will actually execute. Instead defer this to execution time and insert the default PATH at that point if one is not present. Doing this in solver/llbsolver/ops/exec covers all executors and also avoids breaking the cache. Client compatibility is handled via a new capability. Fixes #604 Signed-off-by: Ian Campbell <ijc@docker.com>		2018-09-28 14:16:47 +01:00
..
build.go	llbsolver: use result type with multi ref support	2018-07-12 17:52:23 -07:00
exec.go	Push setting of default PATH down into the executor(s)	2018-09-28 14:16:47 +01:00
source.go	source: image source platform support	2018-06-25 10:39:17 -07:00