auto-rebuild images after package sync (or rebuild images nightly)

[rursprung]

right now (2025-01-05) the current images (as listed on docker hub) are from 2024-12-03, however on 2024-12-31 a new for jazzy has been done.

it'd be great if the tooling could somehow be automated to automatically build a new image after every sync.
as an alternative - which might be even better - the images could just be rebuilt e.g. daily. rebuilding the images often is one of the docker best practices and would also help in reducing the reported amount of vulnerabilities on the docker images on docker hub (since these vulnerabilities come from dependencies which tend to be fixed in the mean time).

whatever rebuild policy is being chosen: it'd be great if the README would clearly state when the images get rebuilt.

[mikaelarguedas]

Thanks for reporting, this is the goal (lots more details on 112)

This is currently blocked by docker-library/official-images#17960

Each image will contain the rosdistro sync date in the environment and a new image will be built with that updated env var at each sync,

Hope this helps,

[rursprung]

thanks! but i think #112 is only half the story here since the dockerfiles still need to be updated?
e.g. right now it still refers to an older sync date:

docker_images/ros/jazzy/ubuntu/noble/ros-core/Dockerfile

Line 35 in 0feec48

ENV ROSDISTRO_PKGS_SYNC_DATE=2024-11-21

[mikaelarguedas]

the dockerfiles still need to be updated?

This is a requirement from the official docker images processs: the only way to trigger a rebuild is to modify the dockerfiles and then submit the new dockerfiles by making a PR to their repo with the new commit hash

right now it still refers to an older sync date:

Yes, that PR introduces the element we need in the dockerfile to then be able to automate the file modification and the PR submission on their repo. We need first that PR to be merged for follow-up PRs to be created
That's what I meant by the fact that this is currently blocked.