Doug Davis 64aac182d6 Fix processing of unset build-args during build ... This reverts 26103. 26103 was trying to make it so that if someone did: docker build --build-arg FOO . and FOO wasn't set as an env var then it would pick-up FOO from the Dockerfile's ARG cmd. However, it went too far and removed the ability to specify a build arg w/o any value. Meaning it required the --build-arg param to always be in the form "name=value", and not just "name". This PR does the right fix - it allows just "name" and it'll grab the value from the env vars if set. If "name" isn't set in the env then it still needs to send "name" to the server so that a warning can be printed about an unused --build-arg. And this is why buildArgs in the options is now a *string instead of just a string - 'nil' == mentioned but no value. Closes #29084 Signed-off-by: Doug Davis <dug@us.ibm.com> (cherry picked from commit cdb8ea90b0) Signed-off-by: Victor Vieux <vieux@docker.com>		2016-12-09 14:24:00 -08:00
..
backend.go	Move engine-api client package	2016-09-07 11:05:58 -07:00
build.go	use router.Cancellable instead of direct CloseNotify	2016-03-25 11:33:54 -07:00
build_routes.go	Fix processing of unset build-args during build	2016-12-09 14:24:00 -08:00