Not able to launch about panteras HOT 7 CLOSED

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

from panteras.

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...

from panteras.

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.

from panteras.

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 [email protected] 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.

from panteras.

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

from panteras.

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

from panteras.

fixed

from panteras.