[Spce-user] sipwise as Docker.io container?

chymian chymian at gmx.net
Mon Mar 31 06:59:13 EDT 2014

hey dear fellows,
 +1 for dockerize sip:providerCE

Am Freitag, 28. März 2014, 11:49:42 schrieb Thomas Strobel:
> On Fri, 2014-03-28 at 11:21 +0100, Michael Prokop wrote:
> > * Alexander Lutay [Fri Mar 28, 2014 at 11:07:49AM +0100]:
> > > On 28/03/14 10:33, Thomas Strobel wrote:
> > > >I wondered if you had any thought about providing a docker.io container
> > > >(https://www.docker.io/) for sip:provierCE? It would be great if I could
> > > >test and install sipwise that way! :)
> > 
> > > Does Debian container is already available?
> > > It should be built before sip:provierCE container building.

yes docker.io is available for debian.

 Package: docker.io
 Version: 0.9.0+dfsg1-1 in jessie & sid
 but that is for the host only.

debian containers in all flavours: oldstable, stable, testing, sid, exp., are public available, as well as make-scripts.sh, starting from debootstrap, for the basic image.

> > > Anyway thank you for suggestions, we will think about Docker!
> > 
> > > At the moment we can suggest you try Vagrant, VmWare or VirtualBox
> > > images: http://www.sipwise.com/doc/mr3.2.1/spce/ar01s04.html#_using_a_pre_installed_virtual_machine

instead of using a debian system to host the containers, it would probably be preferable to use a PaaS system like core.os https://coreos.com/
or the _very_ promising DEIS http://deis.io/[1] 
that would help boost security and you could easily scale sipwise on a cluster, creating a 12 factor app. /http://12factor.net//[2]
– that is, where the future knocks on your door – and continuous integration and deployment is a breeze.

> Or maybe one could write a Dockerfile template, based on the
> Debian/Ubuntu container, for installing sipwise?

for containerizing diff. processes/services in their own containers, that would most likely make an extended vagrant file, ala deis is using one.
to just set sipwise up in one container, should be easy, but doesn’t meet the goal of "containerized services” aka. one container per service like i.e. proxy, or webserver.

for wrapping your brain around docker.io and getting your hands dirty, there are a few articles, which are quit enlightening on “dockerization”:

heise: developer (german)
and ff.

and the articel series from lucas carlson (english)

best regards

[1] http://deis.io/
[2] http://12factor.net/
[3] http://www.heise.de/developer/artikel/Anwendungen-mit-Docker-transportabel-machen-2127220.html
[4] http://www.centurylinklabs.com/tag/docker/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20140331/a328a56a/attachment-0001.html>

More information about the Spce-user mailing list