[09:59] Hi everyone. [09:59] I'm trying to use netplan CLI inside a k3s cluster job container but am receiving the following error "Failed to connect to bus: No data available". [09:59] Any clue what i can do to be able to use it successfully? [10:05] Hi there, are your getting this from "netplan apply"? [10:09] yes [10:11] so, netplan will try to reload systemd-networkd or network-manager to apply configuration, their cli tools use dbus to communicate with the backend. I suppose you don't have any of these things running inside your container? [10:12] also, out of curiosity, what is your use case exactly? [10:39] i'm building a system that runs on a air gapped (no internet) environment that has the feature of setting the IPC's network settings [10:39] Right now i'm able to change netplan config file but then i can only use reboot for it to take effect and even then sometimes it works sometimes it doesn't [10:40] "I suppose you don't have any of these things running inside your container?" [10:40] I don't think so, no [10:51] right, it seems to me that, in your scenario, it's better to leave the network configuration to the CNI plugging itself. Like, describing what you need in the pod yaml [11:14] but my intent is to change the host network, would that work that way? [11:17] hmm I see, that wasn't clear to me. In this case I think you can try to use the netplan dbus interface to apply changes to the host. I'm just not sure how to send messages from inside the pod to the dbus daemon running in the host... [11:18] there are some examples here https://netplan.readthedocs.io/en/stable/dbus-config/ [11:19] maybe something like this https://unix.stackexchange.com/questions/546726/setup-docker-container-to-communicate-with-host-over-d-bus [11:27] i completely missed that dbusconfig docs page, i will try that. Thanks (y)