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.
