Hi.

I've improved the process of setting up the docker test environment in
order to try and get some convergence with the VM built by packer.

I've committed the Dockerfile and associate bits in my git repo [4], and
cleaned up the documentation in the wiki [3].

I hope this is much cleaner and straightforward now.

I'm using a variant of baseimage-docker, as explained before, without
mentioning any more manual setup of several layers of images in the wiki
page.


I'm running the test suite on the 5.3 branch inside a container at the
moment, and it's as fast as expected, i.e. still a bit slow when
restoring the DB :-)


Note that the Dockerfile reuses the same
packer/scripts/fusionforge-source.sh script as for packer/vagrant ;-)

Now, when Vagrant 1.6 is available, as it includes support for docker
[5], I guess this could all be merged in a single solution, using
vagrant + docker, which, when run on GNU/Linux, would get maximum
performance, by running a bare docker container, while allowing Windows
of Mac hackers to run the same inside a Virtualbox VM. And guess what,
vagrant seems to be using baseimage-docker too ;)

Any comments / tests welcome.

Best regards,

[3] https://fusionforge.org/plugins/mediawiki/wiki/fusionforge/index.php/Docker
[4] 
https://fusionforge.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=fusionforge/users/olberger.git;a=shortlog;h=refs/heads/docker
[5] 
http://www.vagrantup.com/blog/feature-preview-vagrant-1-6-docker-dev-environments.html

Olivier Berger <[email protected]> writes:

> Yeah, sorry about the mess. Given the tests I've done, the more sensible
> option for now would probably be to start over a Debian version of
> baseimage-docker, which provides openssh and runit over a base Debian
> install, and just document installation of postgres, apache and
> fusionforge.
> I've cloned the baseimage-docker repo and made changes for such a Debian
> base image (theirs provide Ubuntu), even though I haven't checked all
> options, like using a SSH key for connecting to the containers. You'll
> find my "fork" at [1]. It was quite quick and dirty, in order to replace
> the previous attempts at installing runit manually, which is documented
> also in the wiki page (and could probably soon be removed, if the
> Debian baseimage-docker option seems valid), and I'm not sure I'm the
> first one to have initiated this (I received to feedback to my
> announcement on their "private" forum [2]...).
>
> Hope this is clearer now.
>
> Best regards,
>
> [0] http://phusion.github.io/baseimage-docker/
> [1] https://github.com/olberger/baseimage-docker/tree/debian (on a
>     'debian' branch)
> [2] 
> https://groups.google.com/forum/#!searchin/passenger-docker/debian/passenger-docker/4E0c4Z6fGrU/_MHhghbpqqkJ
>     (requires subscription :-/)
>

-- 
Olivier BERGER 
http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)

_______________________________________________
Fusionforge-general mailing list
[email protected]
http://lists.fusionforge.org/cgi-bin/mailman/listinfo/fusionforge-general

Reply via email to