Community mailing list archives

Re: Dockers for OCA/OCB

El Aleman, David Arnold
- 10/20/2015 14:56:48
Here is the a discussion advancing about general tooling requirements:

Here is a design proposal, I;m happy to adapt:
Note the vision in the travisfiles2dockerfiles section and teh dockerfiles with batteries section...

El mar., 20 oct. 2015 a las 13:47, David Arnold (<>) escribió:
As I laid out on the Other thread (Recommended Contributor Tooling (RCT)), I would be in favor of a PR in the form of a (minimalist) proposal, to discuss technical details and let available knowledge influence at each step of the design process. 
We are through a whole lot of learning curve here as well, the logging is for example taken care by the docker logging driver. I don't see so much of a pain, there...
For example, in your dockerfile, the section
apt-get update && \
apt-get -yq install \
is quite static. Please make yourself familiar with the approach proposed by moses on travisfiles2dockerfiles, to have a possibly more elegant and dynamic solution there. I also don't see the point of loading any source code, which is subject any workingdirectory into the dockerfile, at least not from a remote source! This is likely to be overwritten anyhow.

Well, those are just some quick comments, the rest is not so much different from the official odoo package, right?

Here you can see a runfile, that gives some debugging output, and is very flexible, you specify the code you want to run, by just specifiyng the folder name in the source directory as a docker command. So, this is inherently for any possible odoo, you can imagine.
But for me this is still not good enough! That's why the initiative to port voodoo to go... Have a binary, who takes care of all the github stuff, and the configuration of docker-command. 

I would prefer not to rely on docker-compose on the outside docker, but rather chose a docker in docker strategy with the privileged flag, as laid out in the other post. Although docker-compose is on windows now, this is non-necessary (!) local host tooling. We just can avoid this, because we can! :)

El mar., 20 oct. 2015 a las 0:42, Caudal Eric (<>) escribió:

Hi Rafael,
Thanks for the feedback.
Let's wait for interest and potential contributors before changing something which is currently satisfactory.

On Tue, Oct 20, 2015, 09:56 Raphaël Valyi <> wrote:
Hello Eric,

As for Voodoo, we could bring it to the OCA umbrella. But honestly this isn't a huge project and we are doing very well maintaining it so the OCA structure is overkill for it. Meanwhile contribs to Voodoo are welcome too and we hope the OCA people will find it useful as we do. We will present this dev tool extensively in the coming weeks, but sorry as for now we have no time for that, so I was just answering that point.


On Mon, Oct 19, 2015 at 11:47 PM, Caudal Eric <> wrote:
     Dear community contributors,
We are currently using docker for our infrastructure and it has been quite a challenge to finetune the setup and deployment but we are finally getting there.

A difficult but fruitful learning
Besides we have an additional constraint which was to be able to execute Odoo in China which was challenging because Google content is currently blocked here.
We have tried many options and dockers but we wanted to automate as much as possible the docker creation and mirroring to China which we actually succeeding.
Versions of docker have evolved quite a lot and we recently came to the decision to deploy with docker-compose. There are still some shortcomings (log management is a pain) and bugs (if a download fails you need to restart docker for the server which is restarting all services...).
We are still on the way but we are quite happy with the result were now we can deploy in 5 min any github Odoo specific repository.

Odoo in docker
Our dockers are based on OCB, for v7, v8 and v9.
Chinese dockers are available for v7 and v8.
Chinese v9 will come in few days: they are based on OCB and replace all forbidden content by local mirrors.
For obvious reasons Enterprise will have to be built by the partners themselves on top of the v9 community docker.

Our dockerfiles are here:
You can download the dockers here:

NB: Actually, you can speed up docker download in China by adding in your /etc/default/docker file the following:
(or your favorite mirror for other countries) and restart the service.

How to get started
(a very quick one: we will publish a complete blogpost soon)
You need to install docker (>1.8) and docker-compose in your vm:
Launch the command to pull docker images:
- docker pull postgres:9.4
- docker pull elicocorp/odoo:9.0
(or docker pull elicocorp/odoo-cn:8.0 if you want version 8 of the Chinese code)
- Create a specific directory and create one file docker-compose.yml for postgresql and Odoo (we will soon push an example in our github)
- docker-compose up
et voilà Odoo will be available at port 8069.

We will publish in the coming days additional resources to automate the install for separate repos at docker build.

Contributing to OCA
Now, some contributors are having interesting discussions about recipes, voodoo, dockers etc. They are all interesting tools and probably complementary. Objectives of the users might be very different and each tool will bring advantages accordingly.

Everybody is welcome to propose contribution to our repository but we think it could be the moment to start having proper docker technology for the OCA.
Who would be willing to contribute?
I would propose to create a repository packaging (where we could find the anybox-buildout, docker files, voodoo and/or other packaging tools)
For docker files, we could start the contribution by pushing our code to the OCA or of course any other good alternative.

Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APAC

Eric  Caudal (from my mobile)

Post to:

Raphaël Valyi
Founder and consultant
+55 21 3942-2434



Eric  Caudal (from my mobile)

Post to: