See:
The docker image always lags behind a new LTS release. Any chance to get some automation done to update to latest LTS as soon as it is released?
The whole process can be done in continuous integration. It seems to me as simple a creating a new job on https://ci.jenkins.io/ (but I could be wrong).
Automated builds are in jenkinsci/jenkins:lts already
Docker-Official jenkins image needs manual steps
For reference, what are these manual steps that can't be automated?
My own image does FROM jenkins:2.46.1 and I still can't update it after 3 days since Jenkins 2.46.1 has been released.
The "official" Docker Jenkins images require pull requests like this one.
Frankly, there's no benefit to using the Docker "official" images. Instead I suggest you rely on jenkinsci/jenkins:2.46.1 which is the official (from the Jenkins project) image for that LTS release.
@rtyler thanks, the difference between docker-official and jenkinsci isn't obvious. Switching to jenkinsci/jenkins:lts seems indeed the right thing to do ... once you're informed about it.
Most helpful comment
Automated builds are in jenkinsci/jenkins:lts already
Docker-Official jenkins image needs manual steps