Epic: Make Compose a Docker container

[bfirsh]

$ docker run compose up

Update, 2015-03-10: #619 is the first step towards this, but we still have to pass loads of options to docker run to make it work properly. Next step is figuring out if we can make any changes to Docker so we don't have to pass these options – e.g. some way of setting default options for an image, some way of passing the Docker socket through to the container, etc.

[aanand]

This so much. fig should be an alias to docker run [some flags] fig.

Main issue, off the top of my head, is reading the local filesystem. Easy enough to mount the current directory (something like docker run -v $(pwd):$(pwd)), but what if there are keys in the YAML like build: ../sibling-dir or build: /some/other/dir/entirely?

The solution might be to not support paths outside the current directory.

[renato-zannon]

Maybe mount all external dirs using -v? So a build: /foo/bar could become docker run -v /foo/bar:/build

[prologic]

Perhaps fig should remain a tool and not a Dockerized container/service :)

[prologic]

On Wed, Aug 20, 2014 at 6:54 PM, Omer Katz notifications@github.com wrote:

If fig could be a docker container it would be possible to use it with
boot2docker.
That would be helpful for all those OSX/Windows users out there.

Wait what? I (and I assume others) already use fig + boot2docker
quite successfully. I'm not sure how fig is not working for you?

cheers
James

James Mills / prologic

E: prologic@shortcircuit.net.au
W: prologic.shortcircuit.net.au

[prologic]

I don't understand. What doesn't work for you?

cheers
James

James Mills / prologic

E: prologic@shortcircuit.net.au
W: prologic.shortcircuit.net.au

On Thu, Aug 21, 2014 at 4:18 PM, Omer Katz notifications@github.com wrote:

I found no info about that. Not in the docs and not on #docker on irc.

—
Reply to this email directly or view it on GitHub
#169 (comment).

[TylerJewell]

We are working on one for Codenvy - so that each project can have a Runner
environment with fig pre-installed. Our Runner environments are individual
docker containers.

This is for our new system, which we have been building for 3 years, and
will ship this quarter. We've had to build a few dozen hardened docker
images, for a variety of runner types for various projects within the IDE.
Now we want runners to be extendable via fig configurations.

Will probably have something to share with the group in a couple days.

Tyler

Tyler Jewell -- ceo @codenvy.com -- +1 978-884-5355 -- Schedule Appt.
https://codenvy.appointlet.com/ -- Blog http://blog.codenvy.com

On Wed, Aug 20, 2014 at 11:49 PM, James Mills notifications@github.com
wrote:

I don't understand. What doesn't work for you?

cheers
James

James Mills / prologic

E: prologic@shortcircuit.net.au
W: prologic.shortcircuit.net.au

On Thu, Aug 21, 2014 at 4:18 PM, Omer Katz notifications@github.com
wrote:

I found no info about that. Not in the docs and not on #docker on irc.

—
Reply to this email directly or view it on GitHub
#169 (comment).

—
Reply to this email directly or view it on GitHub
#169 (comment).

[damnhandy]

@therealprologic I think he's referring to Fig on Windows. On OS X all is well, but running Fig under Windows isn't particularly easy.

[prologic]

Running anything non-GUI isn't aprticularly easy on Windows? :)

To be fair however I have run and developed Python-based apps
on Windows just fine. Python 3 makes this a lot easier nowadays.

cheers
James

James Mills / prologic

E: prologic@shortcircuit.net.au
W: prologic.shortcircuit.net.au

On Sat, Oct 18, 2014 at 4:37 AM, Ryan J. McDonough <notifications@github.com

wrote:

@therealprologic https://github.com/therealprologic I think he's
referring to Fig on Windows. On OS X all is well, but running Fig under
Windows isn't particularly easy.

—
Reply to this email directly or view it on GitHub
#169 (comment).

[dduportal]

Ping @bfirsh :
#598

I provide since a bit of time this image : https://registry.hub.docker.com/u/dduportal/fig/ .
But the filesystem problem that @aanand spoke is a real struggle for beginners : i have this issue as concrete example : https://github.com/dduportal/dockerfiles/issues/4 .

Maybe the command that will run fig inside a container should try a big "/" mount in privileged mode, in order to get the docker host and container in sync ?

Don't we depend on the "docker -v" future (streaming from local client to daemon the files) ?
I propose to write a bit of doc if provided officially that way, forbidding relative path, or at least warning the user, what do you think ?

[dduportal]

OK, some thoughts around that :

• Fig relative path resolving
  If i understand well this function - https://github.com/docker/fig/blob/fd30920aac060b03d6e67ec5c3170f670a73d00e/compose/service.py#L590 - fig will just ask Python to resolve the full OS path, so locally.
• The struggle : fig should be running as close as possible as the host, in order to guarantee absolute file path homogeneity
• To illustrate : the wordpress example on the fig website only work if the absolute file path exists both on the docker client OS and the docker HOST. I tried to run the example on Mac OS with boot2docker :
  • From a folder which is inside /Users (auotmounted to /Users by boot2docker) => perfect
  • From another folder (like /tmp for reproducing), /code volume of the 'web' service will be empty because the folder doesn't exists in b2d filesystem

I'm thinking about that kind of thing :

• If running fig inside a container, providing a way to fig to know it
• Running that container, auto mounting the all / in /hostroot for example and use workdir to /figroot/$(pwd) :

docker run -w /figroot/$(pwd) -v /:/figroot -ti dduportal/fig up -d

• When in that case, fig will resolve the "external" path to /figroot/.....

This is a fig inside container solution, and the perfect solution will be with that moby/moby#7249, but it doesn't seems very simple...

[thaJeztah]

Looks like you need to rename your repository to docker-compose soon, Damien :)

[bfirsh]

Also see #619