As the wait-for-it script is started before the parsing of the command
line, it is always started. It can be a problem if a user wants to start
some other binary than odoo (for example a shell).
Also, the wait-for-it script is only checking if a port is open on a
host and then waits 5 seconds before starting Odoo.
With this commit, the wait-for-it script is replaced by a more useful
custom python script that checks if the postgresql server is able to
handle a connection with the given parameters. Odoo then starts whenever
it's ready or fails after a 30 sec timeout.
In some situations, like when a docker compose file use a data volume
to persist postgresql databases, the Odoo server starts and tries to
connect to database server before the postgresql server is ready.
In such a case, the Odoo containers fails to start.
With this commit, the wait-for-it script is used to wait for the
database server service to be ready before starting Odoo.
This script is available as a Debian package.
Closes#258, closes#259
While phonenumbers is not required to run Odoo, it's a requested nice to
have.
To avoid a red warning while installing num2words with pip, the Debian
backport repository is used.
Also use Debian slim images to gain some space.
closes#245 and closes#168
At build time, curl is used to download gnupg keys without any
verification.
This does not meet the Docker hub requirements:
https://github.com/docker-library/official-images#security
With this commit, gpg is used to download the keys with the best method
specified in the requirements.
the release timestamp and the verification sha1 are now using an ARG
instruction.
It means that they can be specified on the command line argument at the
build time.
When printing a report, the asian fonts were missing.
Also, since Odoo 12.0, rtlcss is needed to support the right-to-left languages
in the Odoo UI.
With this commit, the noto-cjk fonts are added as well as the nodejs rtlcss tool.
As the Odoo Docker images are based on Debian Jessie and Stretch, they
use the postgresql-client package from the respective Debian repo.
The backup feature of Odoo uses the postgresql-client. As a consequence,
if a database server newer than the client is used, the backup may fail.
For example, when using the Odoo Docker image 10.0 against a postgresql
server 10.0, the backup fails.
With this commit, the latest postgresql-client is used from the Postgres
repository. As they seem to be backward compatible, the Odoo backup will
succeed wathever the client/server combination.
fixesodoo/odoo#30599
In Odoo, ldap, qrcode and vobject python modules are set as required in
odoo/setup.py. On the other hand, they are only recommendend in the
Debian package.
As a consequence, it was difficult to run some Odoo modules that
required one of them.
The Odoo Debian package was adapted in master where they were added as
dependencies in odoo/odoo@2ff49c5fcb .
With this commit, they are installed in the Docker images.
This is a part of the fix of odoo/odoo#27752.
locale settings does not need to re-genreate c.utf-8 as it's already
included in Debian Stretch. Also LANG is enough to define the locale
needed by Odoo. Finaly, apt-get does not really need to be explicitly
set in non interactive mode. apt-get is able to do the right thing.
Thanks @tianon
We were still trying to make the auto reload feature work with the 8.0
way in the dockerfile 9 and 10. This patch install the dependency used
in Odoo 9-10 (watchdog instead of pyinotify) and remove the
"auto-reload" key from the default configuration file, as the new syntax
is "--dev=reload".
The auto-reload is now disabled by default (it didn't work, let's not
bother someone that does not need it). The easiest way to use it is to
pass the arguments to the odoo process as:
docker run -p 8069:8069 --name odoo --link db:db -t odoo:[9.0|10.0] -- --dev=reload
fixes#84fixes#98
When using an Odoo subcommand, the name of this subcommand has to be in
first position in the arguments list. Just pass the postgres config at
the end of the command... except for the scaffold one.
Fixes#83
We tried to remove usage of environment variables to set the connection
parameters to the postgres database but we omit the case when they're
set in the config file
related to a3d207fFixes#80
When nothing is passed as argument to the docker container, the
entrypoint will receive the content of the CMD of the dockerfile. In
this case we have to pass the database configuration arguments, else
Odoo won't run correctly. This is the case when you run the command of
our documentation:
``` docker run -p 8069:8069 --name odoo --link db:db -t odoo ```
However, it should still be possible to run custom command (like `ls /`).
Defaulting USER to postgres does not make sense as odoo prevents
creating a database with the user `postgres` (however, there's a bug
that allows it when set by environment variable, but still it does not
work later because Odoo does not use the environment variable to find
the databases in the `list_dbs` method).
Defaulting PASSWORD to odoo makes sense because it's what we set in
the documentationm and is even mandatory since we chose to pass the pg
connections parameters[1] and we did not set a default value for it.
[1] a3d207f2d4
Do not assume that Odoo will handle correctly the PG* environment
variables, because it won't.
We also rename the PG* variables in order to avoid confusion since we do
not export them anymore.
