Skip to content

ci: prove the System packages update, as the core runs it now, leaves Docker alone - #16

Merged
inkly merged 1 commit into
mainfrom
ci/docker-excluded
Oct 8, 2026
Merged

inkly merged 1 commit into
mainfrom
ci/docker-excluded

Conversation

@inkly

@inkly inkly commented Oct 8, 2026

Copy link
Copy Markdown
Collaborator

A fourth mode for the measurement harness, excluded: it starts a box on the newest Docker 28 with a 29 on offer, builds the explicit list the core's System packages update now installs (what a plain upgrade would upgrade, minus Docker's family, simulated once more as the list it is), and runs it the way the core runs it (a transient unit, DEBIAN_FRONTEND=noninteractive, --only-upgrade --no-install-recommends, DPkg::Lock::Timeout=120). docker-upgrade-report.py says, for that run: Docker's packages unchanged, dockerd not restarted, the engine the same, dockerd answering in every sample, every container running throughout, AppManagement not restarted, apt never unpacking a Docker package. Tests for the report cover each way it can fail.

Run 37819769398: Ubuntu 22.04 amd64 and arm64 and Ubuntu 24.04 (needrestart installed) all pass 7 of 7: docker-ce 28.5.2 unchanged with the 29 on offer, 22 to 24 other packages upgraded, dockerd's pid unchanged, no sample without every container. This is the apt-level proof of ReCasaOS/CasaOS#14.

@inkly
inkly merged commit ad2aae5 into main Oct 8, 2026
9 checks passed
@inkly inkly mentioned this pull request Oct 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant