Skip to content
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

failed to create DBus connection: dial unix /var/run/dbus/system_bus_socket: connect : no such file or directory #346

Open
SharonBX opened this issue Jul 1, 2024 · 1 comment

Comments

@SharonBX
Copy link

SharonBX commented Jul 1, 2024

Bug Description

hello , not sure what im doing wrong but i have

[root@bada-bing-workerbm-0 cbis-admin]# runc -v
runc version 1.1.12
commit: v1.1.12-0-g51d5e94
spec: 1.0.2-dev
go: go1.21.9
libseccomp: 2.5.2

and
[root@bada-bing-workerbm-0 cbis-admin]# containerd --version
containerd github.com/containerd/containerd v1.7.16 83031836b2cf55637d7abf847b17134c51b38e53

(upgraded from containerd containerd.io 1.6.31 by just untar containerd-1.7.16-linux-amd64.tar.gz , hope its good enough )

after installing all nri pods failing with
[root@bada-bing-workerbm-0 cbis-admin]# kubectl logs nri-resource-policy-balloons-kssz7 -n kube-system
Defaulted container "nri-resource-policy-balloons" out of: nri-resource-policy-balloons, patch-runtime (init)
time="2024-07-01T06:54:07Z" level=info msg="setting up D-Bus connection..."
time="2024-07-01T06:54:07Z" level=fatal msg="failed to autodetect container runtime: failed to create DBus connection: dial unix /var/run/dbus/system_bus_socket: connect
: no such file or directory"
[root@bada-bing-workerbm-0 cbis-admin]#

[root@bada-bing-workerbm-0 cbis-admin]# kubectl logs nri-resource-policy-balloons-kssz7 -n kube-system -c patch-runtime
time="2024-07-01T06:53:49Z" level=info msg="setting up D-Bus connection..."
time="2024-07-01T06:53:49Z" level=info msg="looking for active runtime units on D-Bus..."
time="2024-07-01T06:53:49Z" level=info msg="found containerd.service..."
time="2024-07-01T06:53:49Z" level=info msg="enabling NRI in containerd configuration..."
time="2024-07-01T06:53:49Z" level=info msg="restarting D-Bus unit containerd.service..."
time="2024-07-01T06:53:50Z" level=info msg="enabled NRI for containerd.service"
[root@bada-bing-workerbm-0 cbis-admin]#

any idea what am i missing ?

@fmuyassarov
Copy link
Collaborator

@SharonBX do you still have this issue? It could be that the node has more than one container runtime available and the config-manager doesn't know which would it should use to enable the NRI.

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

No branches or pull requests

2 participants