Windows 7 with boot2docker support for fig

[longieirl]

Great experience on a mac running boot2docker and fig, managing my project docker containers! Experience on windows hasn't been great...can load boot2docker, run the different docker containers individually but havent found a solution to getting fig installed! Our project supports different OS and it would be nice to a nice windows experience for developers.

Any links or custom ISO's with fig installed would be great.

J

[jupl]

#417

[josephpage]

#599 boot2docker/boot2docker#603
Using dduportal/fig image in an alias is the best way to deal with fig on Windows :

alias fig='docker run --rm -it \
        -v $(pwd):/app \
        -v /var/run/docker.sock:/var/run/docker.sock \
        -e FIG_PROJECT_NAME=$(basename $(pwd)) \
        dduportal/fig'

[blaggacao]

@josephpage NICE! 😄 This is enough of a solution...

[blaggacao]

after some testing, I noticed, that it should go like this:
into /var/lib/boot2docker/bootlocal.sh

echo 'alias fig='"'"'docker run --rm -it \
        -v $(pwd):/app \
        -v /var/run/docker.sock:/var/run/docker.sock \
        -e FIG_PROJECT_NAME=$(basename $(pwd)) \
        dduportal/fig'"'" >> /home/docker/.ashrc

Note the double-single quote mix, the double quotes inject the single quotes as normal string into the echo evaluation, we need these single quotes here all around, to ensure that $(pwd) etc. are not evaluated too early but only when you actually type in the alias into the shell

you can check the effect of the quoting typing in alias as the docker user after the next reboot

[SvenDowideit]

I wonder if you could move this alias (or as a script) onto the windows box - even if for now you need to leverage boot2docker ssh ... and the vbox share to /c/Users/

[blaggacao]

Sharing with the host for me is another issue of its kind. I'm on hyper-v. Tried some samba but with no avail so far.

Let's say syntactically I perceive boot2docker as my personal entrypoint.

So this little overhead on the persistent layer is ok, I think.

Rather this could go into boot2docker image. Until fig and docker married this might be IMHO a good solution to provide native look and feel of fig on boot2docker... Maybe with a somehow optimised fig-container, the actual one is rather heavy...

[rjoxford]

Amateur question... Where do I add this in? Using Windows 8.1, no idea where to put this. Can't find any bottlocal.sh file... And what would the next steps be? Thanks

[blaggacao]

@rjoxford I added this within the boot2docker image at the described position, so it's within your VM. As boot2docker is largely a non-persisten file system, changes would get lost over a reboot of your VM, but bootlocal.sh resides on a persisten part of the filesystem and like this can write the entry into the aliases every time boot2docker botsup (it is called automaticaly for that purpose).

[dduportal]

Related to #599.

colleague of mine is currently woking on 64-izing boot2docker (network purpose), see https://forums.docker.com/t/32-bits-64-bits-and-tiny-core-linux-6-0-as-a-base-for-boot2docker-iso/722.
Maybe it'll help to run fig inside b2d ?

Otherwise i propose to run fig inside a container : https://registry.hub.docker.com/u/dduportal/fig/ (but it's not the easiest way, see https://github.com/dduportal/dockerfiles/issues/4 for example)

[mikehaertl]

@blaggacao Thanks for the hint on how to install fig. It seems to (almost) work fine. But I have a pretty weird problem now: I try to run a Dockerfile / fig.yml from my repo here:

https://github.com/codemix/yii2-dockerized

This exactly same file works great under Linux und Mac OS X. But if I run this from boot2docker on windows I get this error on fig up:

web_1 | AH00526: Syntax error on line 38 of /etc/apache2/apache2.conf:
web_1 | DocumentRoot must be a directory
yii2_web_1 exited with code 1

Even though the DocumentRoot definitely exists. And the container even starts if I use docker run ... directly.

Any idea, what could go wrong here?

EDIT: I found this question on SO which sounds exactly like my problem. But I can't see where SELinux would be involved here - and why it would still work on Linux/MacOS.

EDIT 2: Created a separate issue for this with more debug output here #994

[mikehaertl]

Ok, I found it out. With the dockerized fig you have to use absolute host paths for shared volumes.

This won't work:

    volumes:
        - ./:/var/www/html/

Whereas this will work:

    volumes:
        - /c/Users/Mike/Documents/yii2:/var/www/html/

[bfirsh]

I have created an issue to keep track of this: #1085. Thanks for reporting!