Not able to launch

[ojilles]

$ ./install.sh -m vagrant

Gives me:

---

==> standalone: Creating vagrant_haproxy_1...
==> standalone: Pulling image haproxy...
==> standalone: Traceback (most recent call last):
==> standalone: File "", line 3, in
==> standalone: File "/code/build/fig/out00-PYZ.pyz/fig.cli.main", line 31, in main
==> standalone: File "/code/build/fig/out00-PYZ.pyz/fig.cli.docopt_command", line 21, in sys_dispatch
==> standalone: File "/code/build/fig/out00-PYZ.pyz/fig.cli.command", line 28, in dispatch
==> standalone: File "/code/build/fig/out00-PYZ.pyz/fig.cli.docopt_command", line 24, in dispatch
==> standalone: File "/code/build/fig/out00-PYZ.pyz/fig.cli.command", line 56, in perform_command
==> standalone: File "/code/build/fig/out00-PYZ.pyz/fig.cli.main", line 427, in up
==> standalone: File "/code/build/fig/out00-PYZ.pyz/fig.project", line 174, in up
==> standalone: File "/code/build/fig/out00-PYZ.pyz/fig.service", line 199, in recreate_containers
==> standalone: File "/code/build/fig/out00-PYZ.pyz/fig.service", line 187, in create_container
==> standalone: File "/code/build/fig/out00-PYZ.pyz/fig.progress_stream", line 37, in stream_output
==> standalone: File "/code/build/fig/out00-PYZ.pyz/fig.progress_stream", line 50, in print_output_event
==> standalone: fig.progress_stream
==> standalone: .
==> standalone: StreamOutputError
==> standalone: :
==> standalone: Error: image library/haproxy not found

[sielaq]

Hi Jilles, sound like you use an old vesion of fig.
same issue was here docker/compose#453
Can you update your fig ?

[ojilles]

root@standalone:/vagrant# docker --version
Docker version 1.3.2, build 39fa2fa
root@standalone:/vagrant# fig --version
fig 1.0.1

I'll try upgrading a few things to see what sticks...

[sielaq]

This could be incompatibillity between fig and docker.
I have successfully tested this combinations:
docker 1.3.1 (4e9bbfa) + fig 1.0.0
docker 1.3.3 (d344625) + fig 1.0.1
which comes with "brew" and boot2docker on MacOS.

I haven't tested with vagrant (Jon did), but problem could be that we use a lxc-docker package from http://get.docker.io/ubuntu, instead of Ubuntu docker.io package (which is very old thats why we do not use it).
I will try with vagrant to reproduce that.

[ojilles]

Thanks, was playing around with it some more, but unsuccessfully (and then got pulled to other things).

On Dec 16, 2014, at 14:02, sielaq notifications@github.com wrote:

This could be incompatibillity between fig and docker.
I have successfully tested this combinations:
docker 1.3.1 (4e9bbfa) + fig 1.0.0
docker 1.3.3 (d344625) + fig 1.0.1
which comes with "brew" and boot2docker on MacOS.

I haven't tested with vagrant (Jon did), but problem could be that we use a lxc-docker package from http://get.docker.io/ubuntu, instead of Ubuntu docker.io package (which is very old thats why we do not use it).
I will try with vagrant to reproduce that.

—
Reply to this email directly or view it on GitHub.

[sielaq]

Ok it was a bug from our side, instalatoin "chicken/egg" problem. First we ned to build images (including DNS) then set up DNS.
fix here:
#10

[sielaq]

keep in mind to clean up your vagrand image with
vagrant destroy
after we merge the fix

[sielaq]

fixed