-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
kic base image: install stable containerd and clean up packages #9135
Conversation
Remove local things from kind, replace with packages. Use the "clean-install" script for a nicer Dockerfile.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afbjorklund 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. @medyagh - what do you think?
A future "optimization" would be to merge the kindbase and the kicbase, to avoid having to first install containerd only to remove it again. We talked about this earlier, but then we didn't want to fork KIND - then again they didn't want to split their "base" either* * into one base, and one containerd Much more details about it in #7788 |
I am re-running the kic base test to see why the failure rate is high. |
docker@minikube:~$ /usr/local/bin/containerd --version
containerd github.com/containerd/containerd v1.3.3-14-g449e9269 449e926990f8539fd00844b26c07e2f1e306c760
docker@minikube:~$ /usr/bin/containerd --version
containerd github.com/containerd/containerd 1.3.3-0ubuntu2 docker@minikube:~$ /usr/local/bin/crictl --version
crictl version v1.18.0
docker@minikube:~$ /usr/bin/crictl --version
crictl version unknown docker@minikube:~$ /usr/local/sbin/runc --version
runc version 1.0.0-rc10
spec: 1.0.1-dev
docker@minikube:~$ /usr/sbin/runc --version
runc version spec: 1.0.1-dev Package versions: containerd/focal,now 1.3.3-0ubuntu2 amd64 [installed,automatic]
cri-tools/unknown,now 1.17.0~3 amd64 [installed]
runc/focal,now 1.0.0~rc10-0ubuntu1 amd64 [installed] |
Hey @afbjorklund a lot of the kic image tests are still failing -- could it be because of the change in versions? |
Possibly, although the cri-tools version was the only one that actually changed (from 1.18 to 1.17). I don't think that any of the patches that kind did on top of containerd 1.3.3 would have that impact ?
https://github.com/containerd/containerd/compare/v1.3.3..v1.3.3-14-g449e9269 And there are lots of 1.3.x releases available since, even if docker 19.03.12 still uses containerd 1.2.13. |
As best as I can tell, the failure is emitted by
Looking at https://serverfault.com/questions/936220/what-could-cause-a-systemd-service-stop-to-end-with-job-being-canceled - this seems to occur when there is a dependency between a service and an unavailable service -- in particular with It sort of sounds like containerd may not be healthy? |
This is easily repeatable locally:
Results in:
|
containerd state is stuck on:
I think the location of containerd changed from
|
|
I hope this helps! |
It does, only removed the symlink and not the actual configuration file Normal installations don't clobber /etc, but install it under /usr/local/lib |
@afbjorklund: PR needs rebase. 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/test-infra repository. |
Included in PR #9330 |
Remove local things from kind, replace with packages.
Use the "clean-install" script for a nicer Dockerfile.
Fixes #8767
Here is the diff, from
container-diff
: