Skip to content

chore(testing): drop debian-11 testing container - #143

Closed
twangboy wants to merge 3 commits into
saltstack:mainfrom
twangboy:remove_debian11_testing_container
Closed

chore(testing): drop debian-11 testing container#143
twangboy wants to merge 3 commits into
saltstack:mainfrom
twangboy:remove_debian11_testing_container

Conversation

@twangboy

@twangboy twangboy commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Summary

Debian 11 (bullseye) reached end of LTS support on 2026-08-31 and no longer
falls under Salt's own supported-OS policy
(Debian oldoldstable is only supported "if it is not EOL"). This removes the
testing:debian-11 image. Debian 12 and 13 remain covered, so overall Debian
test coverage is unaffected.

  • Deletes custom/testing/debian-11.Dockerfile
  • Removes debian-11 from containers.yml's Salt Testing.versions
  • Updates README.md / custom/testing/README.md accordingly

Bonus fix: restore docker coverage on Debian 12/13

Docker was only ever installed on osrelease == '11' in the golden-state-tree
(commit 310cd259, no recorded reason), with pkgs/docker.sls hardcoding the
docker-ce package version suffix to bullseye regardless of release. Dropping
debian-11 outright would have left Debian testing with zero docker
coverage on any release.

Confirmed live that Docker's official apt repo publishes matching
docker-ce/docker-ce-cli builds (including the currently pinned 28.4.0-1)
for bookworm (12) and trixie (13), same as bullseye (11). Made the
pkgver codename-aware and dropped the osrelease == '11' guard so docker
installs on all Debian releases again.

Bonus fix: re-enable vault on Debian 13 (trixie)

The osrelease != '13' exclusion (commit 2dd25b0, Oct 2025) was added
because HashiCorp's apt repo didn't yet publish a Release file for trixie at
the time. Confirmed live that this is no longer the case -
https://apt.releases.hashicorp.com/dists/trixie/Release now returns 200
with a real vault package in the Packages index, same as bookworm. Dropped
the exclusion (the unrelated arm64 exclusion is untouched).

⚠️ Do not merge yet

This is opened as a draft and must stay that way until all three of the
following are merged, since they're what actually stop salt and
salt-bootstrap CI from trying to pull a testing:debian-11 image that no
longer exists:

Once those land, mark this ready for review and merge.

Debian 11 (bullseye) reached end of LTS support on 2026-08-31, and is
no longer covered by Salt's own supported-OS policy (Debian
oldoldstable is only supported "if it is not EOL"). Remove the
testing:debian-11 image now that Debian 11 test coverage is being
dropped from salt and salt-bootstrap.

Do NOT merge this until the following are merged first, or salt's and
salt-bootstrap's CI will break trying to pull a container that no
longer exists:
  - saltstack/salt-bootstrap#2131
  - saltstack/salt#70238
  - saltstack/salt-install-guide#91

Debian 12 and 13 remain covered, so Debian testing coverage is
unaffected overall.
Docker was restricted to osrelease == '11' only (commit 310cd25,
"Remove docker from amazon 2 and debian 12") with no recorded reason,
and pkgs/docker.sls hardcoded the docker-ce pkgver to the bullseye
(11) package suffix regardless of release. Debian 11 is being dropped
as a testing container (EOL), which would otherwise leave Debian
testing with zero docker coverage on any release.

Confirmed live that Docker's official apt repo publishes matching
docker-ce/docker-ce-cli builds, including the currently pinned
28.4.0-1, for bookworm (12) and trixie (13) just as it does for
bullseye (11). Make the pkgver codename-aware and drop the
osrelease == '11' guard so docker installs on all Debian releases
again.

The existing vault exclusion is trimmed to drop the now-dead '11'
entry; trixie (13) is still excluded since HashiCorp doesn't publish
a Release file for it.
The osrelease != '13' exclusion (commit 2dd25b0, Oct 2025) was added
because HashiCorp's apt repo didn't yet publish a Release file for
trixie at the time. Confirmed live that this is no longer the case:
https://apt.releases.hashicorp.com/dists/trixie/Release now returns
200 with a real vault package in the Packages index, same as
bookworm. Drop the exclusion; the arm64 exclusion is unrelated and
untouched.
@twangboy twangboy self-assigned this Sep 4, 2026
@twangboy twangboy closed this Sep 9, 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