<lorbus>
This was part of the fallout from moving to resolved - it adds a `search .` to `resolv.conf` if no DNS servers are explicitly set. This broke node resolution in OKD, I think on OpenStack.
<dustymabe>
AFAIK we (FCOS/RHCOS) already propagate information from `nameserver=` kernel argument to the real root of the machine.
<dustymabe>
in the RFE upstream lennart was proposing systemd just honor the `nameserver=` karg, but we should already have that in *COS
<lorbus>
Well that is not currently respected by resolved
<dustymabe>
but it is my NM, which passes it to resolved
<travier[m]>
If we don't land the Anaconda change, this script will do the change on first boot anyway and then users update and reboot so they won't really see it. But it means that we can not remove it until we have anaconda support
<jlebon>
dustymabe: yeah, that might be the case. we'll find out :)
<dustymabe>
+1
ravanelli has quit [Remote host closed the connection]
<walters>
(i've mooted the idea a few times that we just bring up the interface and do the link-local metadata server request before we do full on DHCP)
saqali_ has joined #fedora-coreos
jpn has quit [Ping timeout: 245 seconds]
saqali_ has quit [Ping timeout: 252 seconds]
saqali_ has joined #fedora-coreos
saqali_ has quit [Read error: No route to host]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 268 seconds]
fifofonix has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<justJanne>
dpkg allows enabling services directly during the package install, is there something like that for rpm-ostree as well?
<justJanne>
e.g. I’d like to automatically install and enable kubelet, if it doesn’t exist yet, and reboot, if it has changed, if it’s not installed yet, via a systemd unit
<justJanne>
I can do rpm-ostree install --idempotent --reboot kubelet, but can I also enable the systemd service of kubelet itself?
<justJanne>
I can’t enable the service via the systemd.units.[].enabled path of the butane config, as the service doesn’t exist during install yet
<justJanne>
I’ll try with the storage.links.[].path workaround
<justJanne>
a different question, is it possible to give a remote tar file as source for a file to be loaded?
jpn has joined #fedora-coreos
mnguyen has quit [Ping timeout: 240 seconds]
mnguyen_ has quit [Ping timeout: 245 seconds]
mnguyen has joined #fedora-coreos
mnguyen_ has joined #fedora-coreos
saqali_ has joined #fedora-coreos
<bgilbert>
justJanne: in Ignition? no.
<bgilbert>
justJanne: if you have a directory tree that you want to provision via Ignition, you might check out the `storage.trees` section in Butane.
crobinso has quit [Remote host closed the connection]
ravanelli has joined #fedora-coreos
ravanelli has quit [Remote host closed the connection]
<justJanne>
bgilbert: does that allow me to merge multiple such trees into the same folder?
<justJanne>
e.g. like unpacking tar files into /usr/local/bin/?
vgoyal has quit [Ping timeout: 252 seconds]
mheon has quit [Ping timeout: 268 seconds]
<walters>
in the general case ignition and butane definitely allow injecting arbitrary files in arbitrary places
<justJanne>
Yeah, that's obvious, but automatically unpacking tar files from remote sources doesn't seem easily supported
<justJanne>
(I want to install packages via ignition that aren't available as rpm)
cyberpear has quit [Quit: Connection closed for inactivity]
<Matthieu[m]1>
wow, if the package has ~20 files, it will be such a pain to install each file separatly via Butane...
<Matthieu[m]1>
question: is that possible to build an ostree image based on the official fedora-coreos ostree image, which contains only the layer to install custom packages, and is compatible to next fedora-coreos ostree updates ?...