Operations and Tools - vec-ltd/odoo-docs GitHub Wiki

Odoo Docker Container

A note that in the official Odoo docker container, they create 2 volumes inside the Dockerfile (meaning you basically cannot get rid of these).

One is in /var/lib/odoo which is the odoo data_dir, and the other is /mnt/custom-addons which is automatically added to the addons list.

This is fine for local development, but the key thing is Docker Volumes persist in between container deployments.

This normally would be desired, but the result is if you redeploy your docker container with new custom addons in the default directory, then you will find docker re-mounts the existing volume into that dir and your new changes will not be reflected.

I've also had instances of local development where the data_dir volume gets dirty and no matter how many times I rebuild the image the old data persists.

So to get around this I typically will have my own odoo.conf file, which specifies some OTHER directories for the data_dir and addons, and then the default docker volumes can remain empty and unused.

I find this is much better for deployments.

Also I typically install all the pip modules into the dist-packages directory to ensure they are available to the Odoo runtime but also again, so that each time I rebuild the image for deployment no cached packages stick around.

Odoo RunBot

Go to this site - https://runbot.odoo.com

It will have different versions of uncustomised odoo available.

By comparing this to your version, you can see if a feature is core odoo functionality, or if it has been customised.