Skip to content

[WIP] Upgrade jessie-dnsutils Debian base image from Jessie to Bookworm #132273

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

[WIP] Upgrade jessie-dnsutils Debian base image from Jessie to Bookworm #132273

wants to merge 1 commit into from
+11 −10

Conversation

TinaMor
Copy link

@TinaMor TinaMor commented Jun 12, 2025 •
edited
Loading

What type of PR is this?

/sig windows
/sig testing

/kind feature

What this PR does / why we need it:

Jessie ELTS support ends on June 30, 2025, after which many architectures (amd64, armhf, etc.) will no longer have archive files, causing frequent 404 errors for jessie-dnsutils. See error log below.

Bookworm is Debian 12 and will be supported with ELTS until June 30, 2033. We could add the failing architectures to:

kubernetes/test/images/jessie-dnsutils/fixup-apt-list.sh

Lines 23 to 30 in d55b119

case ${DEB_ARCH} in
s390x|arm64|ppc64el)
# We have to use the archive mirrors.
# See: https://lists.debian.org/debian-devel-announce/2019/03/msg00006.html
echo "deb http://archive.debian.org/debian/ jessie main contrib non-free" | tee /etc/apt/sources.list
echo "deb-src http://archive.debian.org/debian/ jessie main contrib non-free" | tee -a /etc/apt/sources.list
;;
esac

However, this is not a robust solution. Switching to Bookworm removes the need for those fragile workarounds.

#10 [4/6] RUN apt-get -q update &&     apt-get install -y --force-yes dnsutils &&     apt-get clean
#10 0.181 Ign http://deb.debian.org jessie InRelease
#10 0.216 Ign http://deb.debian.org jessie-updates InRelease
#10 0.232 Ign http://deb.debian.org jessie Release.gpg
#10 0.247 Ign http://deb.debian.org jessie-updates Release.gpg
#10 0.269 Ign http://deb.debian.org jessie Release
#10 0.292 Ign http://deb.debian.org jessie-updates Release
#10 0.417 Ign http://security.debian.org jessie/updates InRelease
#10 0.446 Ign http://security.debian.org jessie/updates Release.gpg
#10 0.475 Ign http://security.debian.org jessie/updates Release
#10 0.511 Err http://security.debian.org jessie/updates/main amd64 Packages
#10 0.511   
#10 0.523 Err http://deb.debian.org jessie/main amd64 Packages
#10 0.523   404  Not Found [IP: 151.101.66.132 80]
#10 0.539 Err http://security.debian.org jessie/updates/main amd64 Packages
#10 0.539   
#10 0.545 Err http://deb.debian.org jessie-updates/main amd64 Packages
#10 0.545   404  Not Found [IP: 151.101.66.132 80]
#10 0.571 Err http://security.debian.org jessie/updates/main amd64 Packages
#10 0.571   
#10 0.600 Err http://security.debian.org jessie/updates/main amd64 Packages
#10 0.600   
#10 0.629 Err http://security.debian.org jessie/updates/main amd64 Packages
#10 0.629   404  Not Found [IP: 151.101.66.132 80]
#10 0.632 W: Failed to fetch http://deb.debian.org/debian/dists/jessie/main/binary-amd64/Packages  404  Not Found [IP: 151.101.66.132 80]
#10 0.632 
#10 0.632 W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages  404  Not Found [IP: 151.101.66.132 80]
#10 0.632 
#10 0.632 W: Failed to fetch http://security.debian.org/debian-security/dists/jessie/updates/main/binary-amd64/Packages  404  Not Found [IP: 151.101.66.132 80]
#10 0.632 
#10 0.632 E: Some index files failed to download. They have been ignored, or old ones used instead.
#10 ERROR: process "/bin/sh -c apt-get -q update &&     apt-get install -y --force-yes dnsutils &&     apt-get clean" did not complete successfully: exit code: 100
------
 > [4/6] RUN apt-get -q update &&     apt-get install -y --force-yes dnsutils &&     apt-get clean:
0.600   
0.629 Err http://security.debian.org jessie/updates/main amd64 Packages
0.629   404  Not Found [IP: 151.101.66.132 80]
0.632 W: Failed to fetch http://deb.debian.org/debian/dists/jessie/main/binary-amd64/Packages  404  Not Found [IP: 151.101.66.132 80]
0.632 
0.632 W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages  404  Not Found [IP: 151.101.66.132 80]
0.632 
0.632 W: Failed to fetch http://security.debian.org/debian-security/dists/jessie/updates/main/binary-amd64/Packages  404  Not Found [IP: 151.101.66.132 80]
0.632 
0.632 E: Some index files failed to download. They have been ignored, or old ones used instead.
------

Which issue(s) this PR is related to:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. sig/windows Categorizes an issue or PR as relevant to SIG Windows. sig/testing Categorizes an issue or PR as relevant to SIG Testing. kind/feature Categorizes issue or PR as related to a new feature. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jun 12, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Jun 12, 2025
@k8s-ci-robot
Copy link
Contributor

Hi @TinaMor. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jun 12, 2025
@TinaMor TinaMor changed the title Upgrade jessie-dnsutils Debian base image from Jessie to Bookworm [WIP] Upgrade jessie-dnsutils Debian base image from Jessie to Bookworm Jun 12, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: TinaMor
Once this PR has been reviewed and has the lgtm label, please assign dims for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

This was referenced Jun 12, 2025
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@justaugustus justaugustus Awaiting requested review from justaugustus

@mkumatag mkumatag Awaiting requested review from mkumatag

Assignees
No one assigned
Labels
area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/feature Categorizes issue or PR as related to a new feature. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. release-note-none Denotes a PR that doesn't merit a release note. sig/testing Categorizes an issue or PR as relevant to SIG Testing. sig/windows Categorizes an issue or PR as relevant to SIG Windows. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@TinaMor @k8s-ci-robot