ci: weekly scheduled rebuild of master container images#301
Open
pjordanandrsn wants to merge 1 commit intobrian7704:masterfrom
Open
ci: weekly scheduled rebuild of master container images#301pjordanandrsn wants to merge 1 commit intobrian7704:masterfrom
pjordanandrsn wants to merge 1 commit intobrian7704:masterfrom
Conversation
Currently the four images published by docker.yml rebuild only when a new
release is published. Between releases the :master tags drift behind on
python:3.13 / debian-bookworm OS-package fixes — a trivy scan of the
2025-10-17 images on 2026-05-02 found 154 CRITICAL + 754 HIGH OS CVEs
in each of ots_eud_handler{,_ssl}.
Adding a 'schedule:' trigger lets the existing matrix run weekly so the
:master tags stay current with base-layer fixes between releases. No
source change, no application risk — same Dockerfiles, fresher base.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
The four images published by
.github/workflows/docker.yml(opentakserver,ots_cot_parser,ots_eud_handler,ots_eud_handler_ssl) currently rebuild only when a new release is published. The:mastertags then drift behind upstream Python and Debian security fixes between releases.A trivy scan of the four
:masterimages on2026-05-02(last published2025-10-17) found:ghcr.io/brian7704/ots_eud_handler:masterghcr.io/brian7704/ots_eud_handler_ssl:masterghcr.io/brian7704/ots_cot_parser:masterghcr.io/brian7704/opentakserver:masterAll
eud_handlerfindings are in OS packages of thepython:3.13base. Rebuilding the same Dockerfile with--pullagainst a currentpython:3.13reduces these to zero — no source changes, no application risk.Change
Adds a
schedule:trigger to the existingDocker Image CIworkflow:The matrix already builds all four images with
--pullsemantics viadocker/build-push-action@v6, so no other changes are needed. Weekly cadence matches typical Debian/Python base-image refresh cycles without burning excessive CI minutes.Alternatives considered
schedule:reuses what's already there.Verified locally
Same Dockerfiles built with
docker build --pullagainst currentpython:3.13:ots_eud_handler→ 0 HIGH/CRITICAL OS CVEsots_eud_handler_ssl→ 0 HIGH/CRITICAL OS CVEsHappy to adjust the cron schedule or split into a separate workflow file if preferred.