Delay in Publish to Docker Hub (20250207)

[LuvForAirplanes]

We are waiting on the newest release (20250207) any idea when this will be available? What could be done to reduce the delay to the publish on docker hub?

Any interest in using GitHub Actions to deploy changes live on each tagged release?

[codebykyle]

Seconding this. GitHub Actions to automatically deploy changes would be really great!

[LuvForAirplanes]

Ha, I don't know if it'll happen, but at least this time, it got pushed through!

[LuvForAirplanes]

Another major issue with the containers is that you can never be quite sure what version of the code they are on. During the last update cycle here, we had a terrible time, figuring out which Enterprise commit we should sit on.

In summary, to questions @d-fence

• how can we know what commit was put into a container?
• how do we know which commit of Enterprise will work with a given Enterprise version?

[d-fence]

Hello,
to answer the long time issue of the commit's, we added a dictionary in the release.py during the packaging.
So the information is now available in the Docker container and can be found easily like:
docker run --rm odoo:17.0 python3 -c 'from odoo import release; print(release.repos_heads)'
and it should return something like:
{'odoo': 'ef11898ad0afa4c154c40d224881fde19b7f41ab', 'enterprise': '099aef8e4163ee341757839564e82c8b9f55c374', 'design-themes': '3e1741c2df5e5c17b85ace314552b9089addd5c9'}

About the delay, there is no easy answer. As stated in the FAQ we cannot publish more than once a week. Also it has to be reviewed by Docker and merged if no issue is found ...

[LuvForAirplanes]

Thank-you. I appreciate it. I also appreciate the insight on the reason containers take longer "to market".

[CtrlCarlitos]

@d-fence This is great! Which versions are supported during the packaging?