Hey Matt,
Thanks, yeah I tried this but as you guessed, the output is received as
string, but I want that string to be echoed into my terminal's tty.
I've now switched to building the image using docker-py and Ansible's
docker module,
- name: Build base image
docker_image: path="{{docker_yard_dir}}/base" name="{{docker_image_
namespace}}/trusty-base"state=present
register: docker_build
Any advice on how I can get the stdout info here, would it still be a case
of accessing `docker_build.stdout`?
Also, what about running this as an async job (which I did); is there away
to get an async job to trigger (say via `notify`) a completion message? I
don't mind if it's via email or using one of the push services Ansible can
hook into.
Thanks for your help!
Best, M.
On Monday, 23 March 2015 19:49:12 UTC+5:30, Matt Martz wrote:
>
> I might recommend using 'var' instead of 'msg' in debug. The problem is
> likely that the output contains quotes and is breaking the quoting.
>
> Something like:
>
> - debug: var=docker_build.stdout
>
>
> On Mon, Mar 23, 2015 at 9:13 AM, Mike S <[email protected] <javascript:>>
> wrote:
>
>> Hi all,
>>
>> I've detailed this issue here
>> https://github.com/ansible/ansible/issues/10519
>>
>> To summarise, this was my task,
>>
>> - name: Build base image
>> shell: docker build -t {{docker_image_namespace}}/trusty-base
>> {{docker_yard_dir}}/base
>> register: docker_build
>>
>> - debug: msg="{{ docker_build.stdout }}"
>>
>>
>> and the failure,
>>
>> TASK: [docker-base | debug msg="{{ docker_build.stdout }}"] *******
>> fatal: [10.22.22.22] => A variable inserted a new parameter into the module
>> args. Be sure to quote variables if they contain equal signs (for example:
>> "{{var}}").
>>
>> FATAL: all hosts have already failed -- aborting
>>
>>
>> I've only been able to get this to work as - debug:
>> var=docker_build.stdout, however, this does not print STDOUT, but rather
>> shows the var contents, including '\n' chars in a really long string.
>>
>> Any thoughts on how I can get this sorted?
>>
>> Any suggestions on getting these images built as an async. job as well?
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Ansible Project" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> To post to this group, send email to [email protected]
>> <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/ansible-project/69f2803f-76c8-492a-817e-f79d60148446%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/ansible-project/69f2803f-76c8-492a-817e-f79d60148446%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Matt Martz
> @sivel
> sivel.net
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/7e1bf85f-5fbd-4747-9b48-99b86e0c0ffe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
