Doug Davis 92c353582c Build w/o verbose hangs w/RUN ... `docker build -q .` where Dockerfile contains a RUN cmd will hang on the RUN. It waits for the output stream to close but because of -q we never attached to the container and end up waiting forever. The fact that no one noticed this tells me that people may not actually use -q and if so I wonder if it would make sense to make -q work the may it does for other commands (like `docker ps`) and make it so it only shows the container ID at the end. A -q/quiet option that only hides the container RUN output apparently isn't really that useful since no one is using it. See: https://github.com/docker/docker/issues/4094 Signed-off-by: Doug Davis <dug@us.ibm.com>		2015-02-20 13:38:03 -08:00
..
command	Map Commands instead of using them as a slice	2015-02-20 15:56:21 +01:00
parser	builder/parser: Make use of builder/command	2015-02-11 23:54:41 -08:00
dispatchers.go	Add support for no-arg commands in Dockerfile	2015-02-08 03:36:49 -08:00
evaluator.go	Create builder/command, cut libcontainer dependency on integration-cli	2015-02-11 21:44:31 -08:00
internals.go	Build w/o verbose hangs w/RUN	2015-02-20 13:38:03 -08:00
job.go	Deprecating ResolveRepositoryName	2015-01-08 20:14:58 +00:00
MAINTAINERS	Modify MAINTAINERS per erikh's suggestion	2015-01-05 10:28:36 -08:00
support.go	builder: handle escapes without swallowing all of them.	2014-10-27 17:38:24 +00:00