Community mailing list archives


Re: Official docker images

Vauxoo S.A. de C.V., Moisés Augusto López Calderón
- 13/01/2015 13:20:56
Ok, thank for you reply.

Other matter:
FYI We have a PR to OCA project of a dockerfile here:
And hosted here:

This work with source code directly.
Your feedback is welcome.

2015-01-13 5:23 GMT-06:00 Yannick Buron <>:
Just for those who missed my previous mail about and may be interested, I developed an hosting orchestrator based on Odoo and Docker The concept is to use odoo to orchestrate the hosting of other applications, but you can of course use it to host other odoo instances, with or without the official docker image.

I use it for my own purpose but it's still early alpha and difficult to install so if you're interested I suggest you just subscribe to the mailinglist ( until I announce that it's easier to use. This project is my main priority currently, and I want to be able to provide asap free orchestrator hosting for those who want to help me develop it (I think it's a requirement to implicate people because the orchestrator can't be on the same server that the servers with the docker containers), in the end I want to provide the same service than but with a full open-source and more flexible architecture.

Also, I made contact with Indiehosters ( which want to promote independent hosting of open-source applications, so we can finally compete with GAFA. I suggest you have a look.

Finally for those who want to use odoo and docker, please note that it seems there is some problems when you separate odoo and postgres into separate containers (as I do) the connections are not closing correctly It seems also had the same problem

Thank you for theses official images, docker is an excellent technology and it's a good thing to stick with it.

Le 13/01/2015 08:22, UAB Versada - Andrius Preimantas a écrit :
<blockquote cite="" type="cite">


I don't know how often you guys get "it works on my computer but not on production" kind of situations but from my experience it's usually because of different code versions. The way we deploy system is we checkout Odoo at the same commit for production as custom code was developed upon which makes it less likely for those situations to occur. It is harder to maintain .deb installed odoo instance then git cloned, and former approach does not give such a big advantage compared to later (but I guess it's a different topic)

Would be interesting to hear from Odoo S.A. (@Antony any comments?) the reason for official docker image. Was it done because you encourage Odoo deployment in production as a docker container? Or is it for developers to be able to have faster way of building dev environments?

Andrius Preimantas

On 01/13/2015 02:53 AM, Nhomar Hernández wrote:
<blockquote cite="" type="cite">

2015-01-12 18:42 GMT-06:00 Antony Lesuisse <>:
- apt-get manage all the dependecies (except wkhtmltopdf). - the deb repository is gpg-signed (required for official docker images) By the we are improving our deb packaging to get officially sponsored into debian sid. Updating the deb is as easy as: apt-get update && apt-get upgrade

But time between new package from "blessed debian sid" and packages from nightly is so high.

I prefer git directly honestly, and better controlled and better replicable, but it is a matter of taste.

Saludos Cordiales
Nhomar Hernandez

Post to:

Post to:

Post to:

Moisés López Calderón
Vauxoo - OpenERP's Gold Partner
Mobile: (+521) 477-752-22-30
Office: (+52) 477-773-33-46
twitter: @vauxoo