-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Kicbase: fix docker driver with crio runtime: install dbus #21724
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
base: master
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: obnoxxx 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 |
Welcome @obnoxxx! |
Hi @obnoxxx. 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 Once the patch is verified, the new status will be reflected by the 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. |
a04a725
to
4a996b3
Compare
Can one of the admins verify this patch? |
4a996b3
to
5f0f07f
Compare
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.
@obnoxxx thanks!
deploy/kicbase/clean-install
Outdated
|
||
apt-get update | ||
apt-get install -y --no-install-recommends -o DPkg::options::="--force-confdef" -o DPkg::options::="--force-confold" "$@" | ||
apt-get install -y -o DPkg::options::="--force-confdef" -o DPkg::options::="--force-confold" "$@" |
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.
Can you check and report in the commit/pr message which additional packages are installed, and how this affects the size of the image?
The issue with allowing recommended package is that we may install packages we don't need. The image will grow and will be slower to download and more expensive to server the builds.
In general it sounds like a packaging bug when installing required packages without recommended package ends in failure to use the install packages. We may need to report a Debian bug for this.
Ideally we can explicitly install the missing packages to make the requirement clear and link the Debian bug about this. When the bug is fixed we can remove the explicit requirement.
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.
good points, @nirs! I get why recommended packages were originally excluded. But after @afbjorklund 's analysis in issue #21724, I realized that allowing recommended packages did fix the issue for me. I will check the resulting changes in size and packages and update.
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.
Actually my recommendation was to add the "dbus" package, next to the "systemd" package.
--- a/deploy/kicbase/Dockerfile
+++ b/deploy/kicbase/Dockerfile
@@ -91,7 +91,7 @@ RUN echo "Ensuring scripts are executable ..." \
&& chmod +x /usr/local/bin/clean-install /usr/local/bin/entrypoint \
&& echo "Installing Packages ..." \
&& DEBIAN_FRONTEND=noninteractive clean-install \
- systemd \
+ systemd dbus \
conntrack iptables iproute2 ethtool socat util-linux mount ebtables udev kmod \
libseccomp2 pigz \
bash ca-certificates curl rsync \
The no-install-recommends flag was just the reason to why it was missing in the first place.
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.
In general it sounds like a packaging bug when installing required packages without recommended package ends in failure to use the install packages. We may need to report a Debian bug for this.
I think they use "Suggests", for the things that are nice-to-have...
https://www.debian.org/doc/debian-policy/ch-relationships.html
Recommends
: This declares a strong, but not absolute, dependency. The Recommends field should list packages that would be found together with this one in all but unusual installations.
So it installs "Recommends" by default (and breaks without "Depends")
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.
@afbjorklund wrote:
Actually my recommendation was to add the "dbus" package, next to the "systemd" package.
The no-install-recommends flag was just the reason to why it was missing in the first place.
Got it.
I updated the PR accordingly and with local tests it looks good.
Thanks again for your analysis and recommendation!
/ok-to-build-image |
Hi @obnoxxx, we have updated your PR with the reference to newly built kicbase image. Pull the changes locally if you want to test with them or update your PR further. |
Trying these changes locally, I am unsure how ti integrate possible additional changes withe PR including this added commit. |
Check how this is run in the CI, and use the same command: This should work:
We can probably improve the docs: |
/ok-to-test |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This is great improvement for Docker_Linux tests. It seems that test count is incorrect. Before this change we did not run many tests but they are not counted in the skipped tests. Before
https://storage.googleapis.com/minikube-builds/logs/21681/41822/Docker_Linux_crio.html# After
https://storage.googleapis.com/minikube-builds/logs/21724/41851/Docker_Linux_crio.html |
4b13c2b
to
f817275
Compare
/retest |
This comment has been minimized.
This comment has been minimized.
2c933d6
to
d10bcbc
Compare
This comment has been minimized.
This comment has been minimized.
d10bcbc
to
a83898f
Compare
/ok-to-build-image |
Hi @obnoxxx, we have updated your PR with the reference to newly built kicbase image. Pull the changes locally if you want to test with them or update your PR further. |
a42e9d5
to
360d9e0
Compare
/retest |
This comment has been minimized.
This comment has been minimized.
/retitle kicbase: fix docker driver with crio runtime: install dbus |
/ok-to-build-image |
This comment has been minimized.
This comment has been minimized.
/retitle Kicbase: fix docker driver with crio runtime: install dbus |
Hi @obnoxxx, we have updated your PR with the reference to newly built kicbase image. Pull the changes locally if you want to test with them or update your PR further. |
/ok-to-test |
minikube would not start a cluster successfully with docker driver and crio runtime due to missing dbus packages Adding dbus packages to the kicbase image build lets minikube start to complete successfully. Signed-off-by: Michael Adam <[email protected]> Co-authored-by: Anders F Björklund <[email protected]>
53acf3a
to
cdde98f
Compare
/retest-required |
@obnoxxx: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
&& echo "Installing Packages ..." \ | ||
&& DEBIAN_FRONTEND=noninteractive clean-install \ | ||
systemd \ | ||
systemd dbus \ |
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.
thank you for fixing many of the failures, curious is there any documentation that explains we need dbus ? if there are plz add to the PR description
This comment has been minimized.
This comment has been minimized.
kvm2 driver with docker runtime
Times for minikube start: 46.3s 42.2s 45.1s 40.8s 45.2s Times for minikube (PR 21724) ingress: 20.4s 19.8s 15.8s 15.8s 15.9s docker driver with docker runtime
Times for minikube start: 22.3s 22.6s 23.3s 21.7s 24.2s Times for minikube ingress: 11.6s 10.6s 10.7s 10.7s 10.6s docker driver with containerd runtime
Times for minikube start: 20.9s 23.7s 23.1s 19.5s 23.2s Times for minikube ingress: 20.1s 20.2s 20.1s 20.1s 20.2s |
Here are the number of top 10 failed tests in each environments with lowest flake rate.
Besides the following environments also have failed tests: To see the flake rates of all tests by environment, click here. |
minikube would not start a cluster successfully with docker driver and crio runtime due to missing dbus.
Changing the kicbase build to install the dbus package lets minikube start to complete successfully.
Fixes: #21684