I think it should be the other way around: Odoo should tag releases, and odoo docker should pick a release based on this. Odoo is one rare beast by it's own that does not have any releasing standards by tagging etc. In my opinion it's a gamble when you install something just based on the latest commit. Honestly, i can't understand why odoo is doing it this way..

Releases picked for odoo docker are based on odoo's nightly debian packages, which isn't a real release candidate either.. So if you guys want a different version, then find from https://nightly.odoo.com your version, get the sha1sum for the .deb-file (can be found in the .changes file: https://nightly.odoo.com/16.0/nightly/deb/odoo_16.0.20250422_amd64.changes), and compile your own image.

Or if you feel lazy as I do, then just run the following command inside a cloned odoo docker repo to compile your own odoo 18 image from the latest odoo nightly

docker build \ --build-arg=ODOO_RELEASE=$(curl -s https://nightly.odoo.com/18.0/nightly/deb/odoo_18.0.latest_amd64.changes|grep Version|cut -d '.' -f3) \ --build-arg=ODOO_SHA=$(curl -s https://nightly.odoo.com/18.0/nightly/deb/odoo_18.0.latest_amd64.changes|grep -A3 Checksums-Sha1|tail -n1|awk '{print $1}') \ -t "myodoo16:$(curl -s https://nightly.odoo.com/18.0/nightly/deb/odoo_18.0.latest_amd64.changes|grep Version|cut -d '.' -f3)" \ ./18.0

In my opinion it's a gamble when you install something just based on the latest commit.

I know, right? It's crazy that a company Odoo's size is still doing something like this.

Thanks for the commands.