Wesley Tanaka
Wesley Tanaka
"Could not parse Docker build output for image ID" in docker version 1.12.1 using build_options `-q`
https://github.com/wtanaka/role-tester-ansible/blob/master/.kitchen.yml
"Could not parse Docker build output for image ID" in docker version 1.12.1 using build_options `-q`
I'll update the title ``` /tmp/wtanaka % docker --version Docker version 1.12.1, build 23cf638 /tmp/wtanaka % docker build -q -f Dockerfile . sha256:ff60113363279ed0eb02aadd3149368b414dcf9baa4d3ce3c1fc8b6f4a03875e /tmp/wtanaka % docker build -f Dockerfile ....
"Could not parse Docker build output for image ID" in docker version 1.12.1 using build_options `-q`
`-q` is particularly useful in online CI services which tend to limit the amount of output that you can produce from CI test jobs.
"Could not parse Docker build output for image ID" in docker version 1.12.1 using build_options `-q`
It can add up as the cross product of platforms and suites starts to add up. ``` platforms: - driver_config: {image: 'centos:5'} name: centos-5 - driver_config: {image: 'centos:7'} name: centos-7...
"Could not parse Docker build output for image ID" in docker version 1.12.1 using build_options `-q`
I think the docker output might be spammier than you imagine. I spent a few minutes trying to find an example without `-q` -- I didn't succeed yet, but this...