Installation on OSX with boot2docker

[bwiklund]

FIY, if you're using boot2docker and follow the OSX setup instructions on the site, fig doesn't work (any command just exits siliently)

It does however work if installed via brew. I don't know the reason behind it but hopefully this helps you guys.

[SvenDowideit]

weird! I'll have to get my people to talk to ..... oh yeah ;)

@bfirsh @aanand do you have any debug info about this?

[rcadena]

I'm not sure if I'm experiencing the same issue as bwiklund, but I also am having problems with boot2docker and fig. I tried the quickstart on the fig site. I get as far as downloading and starting up the redis container, but the web container fails to start because it can't find a file I created.

My suspicion is just that the folder mapping is not working between the osx <-> boot2docker's container <-> web container

After fig up, the redis image comes up correctly, but the web container fails with the following:

web_1   | python: can't open file 'app.py': [Errno 2] No such file or directory
fig2_web_1 exited with code 2
Gracefully stopping... (press Ctrl+C again to force)

Then both containers are down after that. I'm certain that the app.py file is in the current directory.

I also tried the django quickstart. In that case, after fig up, the project is created but if I run ls, my local directory does not show the current project. However, if I try to run the django startproject command again it fails because it says a project already exists at the location. Doing an ls my local directory shows this:

figtest: ls
Dockerfile              fig.yml
requirements.txt    

Doing an ls in the web container (fig run web ls /code) shows me this:

figtest: fig run web ls /code
figexample  manage.py

So you can see that the code directory in the web container is not mapping to my local working directory.

Other infos:

• os x 10.9.4
• fig 0.5.2
• docker 1.2.0, build fa7b24f
• boot2docker 1.1.2
• virtualbox 4.3.14 r95030

[huslage]

You cannot mount a local directory inside of a boot2docker container at the moment. See boot2docker/boot2docker#413 for more information.

[HintikkaKimmo]

Hi, I am also experiencing the same with brew install, but not on Ubuntu VM running docker natively. For me its exits with ether error 1 or error 0. Where can I find what these errors actually mean anyway?

First I was thinking there must be something wrong with my fig.yml file as it seem to work perfectly on the first boot but not after but this seems only to be issue if I run those containers in my mac not on top of native linux (only tested Ubuntu)

[aanand]

@HintikkaKimmo Installation via Homebrew is not officially supported. Have you tried downloading the binary?

[panta]

I tried, on OSX, both with the Homebrew versions and the official binary ones, and the results is the same for me, with the problem persisting.
I've just commented the problem here #300 (comment)

Any suggestions?