Noah Kantrowitz
Noah Kantrowitz
@joegoggins Please include your full config file. You might have disabled too much sudo.
"Could not parse Docker build output for image ID" in docker version 1.12.1 using build_options `-q`
Please include your `.kitchen.yml` config. The tests run using the latest Docker so that is not likely the issue.
"Could not parse Docker build output for image ID" in docker version 1.12.1 using build_options `-q`
Does it work if you remove the build_options -q? I'm guessing that suppresses the output we need to parse.
"Could not parse Docker build output for image ID" in docker version 1.12.1 using build_options `-q`
Ahh yeah, as you noted. I probably won't fix that any time soon, the `_options` things are a trapdoor for new Docker features and I don't think there is a...
"Could not parse Docker build output for image ID" in docker version 1.12.1 using build_options `-q`
The limit is usually a few megabytes, the docker build is generally no more than 1k of output. I don't think something less than ~
"Could not parse Docker build output for image ID" in docker version 1.12.1 using build_options `-q`
(also having the build record is super important for replicating failed CI builds sometimes)
"Could not parse Docker build output for image ID" in docker version 1.12.1 using build_options `-q`
That's still only 56 instances. In theory the build output should be cached for every suite after the first on a given platform but even assuming ~50kb of output, Travis'...
"Could not parse Docker build output for image ID" in docker version 1.12.1 using build_options `-q`
Ahh right, I forget not everyone is using the remote mode which disables the build context. That's fair.
"Could not parse Docker build output for image ID" in docker version 1.12.1 using build_options `-q`
There is also a separate flag to disable the build context, but that might not always help.
What scripts do you mean?