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.
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
Restore docker focal version in gci nodes #92344
Restore docker focal version in gci nodes #92344
Conversation
/sig release |
/cc @dims |
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, jherrera123 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
Taking a quick look at the focal repo packages, it is missing s390x and maybe armhf and ppc64el architectures. However, the modified script is for gce, which according to the doc, only supports Intel and AMD CPUs (x86-64), so it shouldn't affect the test negatively. |
/test pull-kubernetes-e2e-kind |
/test pull-kubernetes-e2e-kind |
2 similar comments
/test pull-kubernetes-e2e-kind |
/test pull-kubernetes-e2e-kind |
/test pull-kubernetes-e2e-kind |
/retest Review the full test history for this PR. Silence the bot with an |
/test pull-kubernetes-verify |
/test pull-kubernetes-integration |
/retest Review the full test history for this PR. Silence the bot with an |
/retest |
/retest Review the full test history for this PR. Silence the bot with an |
What type of PR is this?
/kind bug
What this PR does / why we need it:
This change reverts a workaround needed to install docker in ubuntu focal fossa gci nodes.
Which issue(s) this PR fixes:
Fixes #90709
Special notes for your reviewer:
The workaround was installing docker on focal fossa nodes from the bionic repo instead of the focal fossa repo because the focal fossa repo did not exist. Docker team has now created the focal fossa repo, so we no longer need the workaround.
Does this PR introduce a user-facing change?: