When installing postgresql-client, the Debian repo from Postgresql is added as a source list.
As a consequence, when installing the Odoo debian packages, the
package dependencies are also searched in the Postgresql repo.
In this case, it appears that python3-werkzeug version 0.16 was
installed from the Postgresql repo.
Closes#299
Before this commit, the deb package was installed in two steps.
The first step was to use dpkg and force the install, the second step
was to repair the broken install.
Although the `EXPOSE` instruction does not actually publish the ports,
it has an impact on inter docker communication.
With this commit, port 8072 is also exposed.
Closes#107
The Odoo's fallback for the slugify_one method does only support latin
letters. This commit installs the python-slugify library from the Debian
packages.
Closes#199
Thanks to @lem8r for the report and PR.
When creating an apt source list for Postgresql Debian package, the
redirection uses a relative path. It works because the default WORKDIR
but it's a fragile bad practice.
Thanks to @fractalf and @alorence for the bug report and investigation.
closes#287, closes#290
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.
