dustymabe changed the topic of #fedora-coreos to: Fedora CoreOS :: Find out more at https://getfedora.org/coreos/ :: Logs at https://libera.irclog.whitequark.org/fedora-coreos
plarsen has quit [Remote host closed the connection]
vgoyal has quit [Ping timeout: 240 seconds]
gursewak has joined #fedora-coreos
jpn has quit [Ping timeout: 250 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 252 seconds]
gursewak has quit [Ping timeout: 245 seconds]
gursewak has joined #fedora-coreos
paragan has joined #fedora-coreos
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 240 seconds]
sentenza has quit [Remote host closed the connection]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 245 seconds]
jpn has joined #fedora-coreos
sentenza has joined #fedora-coreos
jcajka has joined #fedora-coreos
sentenza has quit [Remote host closed the connection]
mnguyen_ has quit [Remote host closed the connection]
mnguyen_ has joined #fedora-coreos
jpn has quit [Ping timeout: 250 seconds]
plundra has quit [Server closed connection]
plundra has joined #fedora-coreos
jpn has joined #fedora-coreos
plundra has quit [Remote host closed the connection]
plundra has joined #fedora-coreos
saschagrunert has joined #fedora-coreos
jpn has quit [Ping timeout: 245 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 245 seconds]
jpn has joined #fedora-coreos
pwhalen has quit [Server closed connection]
pwhalen has joined #fedora-coreos
jpn has quit [Ping timeout: 250 seconds]
apiaseck has joined #fedora-coreos
<travier[m]> jmarrero: Thanks!
apiaseck has quit [Ping timeout: 245 seconds]
daMaestro has quit [Quit: Leaving]
jobcespedes[m] has quit [Remote host closed the connection]
nbsadminaccount- has quit [Remote host closed the connection]
gnfzdz has quit [Remote host closed the connection]
InshalKhan[m] has quit [Remote host closed the connection]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 250 seconds]
<plundra> (New to coreos; as in have barely booted it) How do people configure "dynamic" storage? In my case, I'd like to assemble all instance storage of an EC2-instance, to raid0 and mount somewhere. The exact path in /dev/disk/by-id varies (serial kinda), and the ignition conf seems to want a list of exact devices?
<plundra> So like, I'd wante devices: to be the list equivalent to /dev/disk/by-id/nvme-Amazon_EC2_NVMe_Instance_Storage_*
hotbox has quit [Ping timeout: 246 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 250 seconds]
jpn has joined #fedora-coreos
<dustymabe> plundra: I think this may be https://github.com/coreos/fedora-coreos-tracker/issues/1122 or https://github.com/coreos/fedora-coreos-tracker/issues/601 - can you weigh in in the tickets?
baude has joined #fedora-coreos
nalind has joined #fedora-coreos
<baude> im trying to understand a problem here where I make some changes to ignition; the changes are reflected in overrides/rootfs but I do not see them *in* the initrd itself. https://paste.centos.org/view/16fa7fd8 shows some details
<baude> am I putting the changed stuff in the wrong spot ?
mheon has joined #fedora-coreos
<plundra> dustymabe: Sure, I'll have a look. Hopefully will get around to test for real to better understand what to ask for too :-)
<plundra> dustymabe: Thanks. And yeah 1122 brings up what I'd like. The /dev/.../ephemeral{N..M}. I guess wildcard expanding into a list is more intrusive to change.
vgoyal has joined #fedora-coreos
<baude> dustymabe: any thoughts? ^^^
plarsen has joined #fedora-coreos
<dustymabe> baude: that looks right..
<baude> i tried --force --force-image on cosa build
<dustymabe> when you boot a built image do you see it in the filesystem?
<baude> lemme see if i have enuff scroll back
<baude> dustymabe: am i just looking for that file ?
<dustymabe> yeah, look for the file to exist and have your modications
<baude> dustymabe: would it be in the build log or you saying i should mount the qcow and poke around ?
<dustymabe> inside the qcow - can you `cosa run` it?
<baude> i get json metadata errors likely because applehv isnt a real platform yet in cosa's mind
<dustymabe> change your command to `cosa run --qemu-image builds/latest/aarch64/fedora-coreos-38.20230621.dev.4-qemu.aarch64.qcow2` and see if that works
<baude> dustymabe: same but i did confirm on the rootfs, the changed file is indeed present
<dustymabe> ok, so now then you need to make sure that file got into the initrd.. if you could boot the thing then you could run rd.break=cmdline and actually look at the file in the initramfs
<dustymabe> or you can just extract the initramfs file and check the contents that way
strigazi has quit [Ping timeout: 240 seconds]
<baude> it boots and fails after ignition and drops me to a command line
<baude> are we sure this is not known by a different name in the initrd?
<baude> b/c even lsinitrd does not show it
<baude> dustymabe: I dont see that file in fcos created images either, so i must be cross-wired somewhere
<dustymabe> meeting, brb
spresti_ has joined #fedora-coreos
spresti has quit [Quit: Leaving.]
spresti has joined #fedora-coreos
spresti has left #fedora-coreos [#fedora-coreos]
<dustymabe> baude: you're right. module-setup just tells dracut what to put in the initramfs - so module-setup itself won't exist in the initrd
<baude> right
<dustymabe> but does lsinitrd show that vsock is getting in the initrd?
<baude> im learning
<baude> yes
<dustymabe> so it's included, but now it needs to get loaded (and nothing is loading it)
<baude> so it looks like i need to use distro.ModprobeCmd() in ingition
<dustymabe> ?
<baude> correct
<dustymabe> you could hack for now and `rd.break=cmdline` then `modprobe vsock` and exit and see if it works
<baude> cmdline is before ignition is run ?
<dustymabe> baude: yes, it should be
<baude> dustymabe: btw, i am using an apple m1 that boots to linux for a cosa machine ... works well and reasonably fast
<dustymabe> baude: send me one
<dustymabe> though I can't promise I won't try to put linux on it (which would invalidate the point of me having it probably)
<baude> well that is what i did
<baude> fwiw, you still gotta have a mini-macos install
jcajka has quit [Quit: Leaving]
<baude> dustymabe: im cooking with gas now!
<dustymabe> baude: nice.. did the rd.break thing work?
<baude> didnt try , i just wired it up ... one more step and i should have usable stuff and can then do some fixes, etc and starting making prs
saschagrunert has quit [Remote host closed the connection]
spresti_ has quit []
spresti has joined #fedora-coreos
plarsen has quit [Ping timeout: 240 seconds]
jpn has quit [Ping timeout: 245 seconds]
JohnnyArcitec[m] has quit [Remote host closed the connection]
plarsen has joined #fedora-coreos
paragan has quit [Quit: Leaving]
Nemric has joined #fedora-coreos
Nemric has quit [Quit: WeeChat 3.8]
Nemric has joined #fedora-coreos
<Nemric> o/ 2 of 3 coreos server are PXE booting for full ram use, Each update will change sshd keys, so I delete odl keys from known hosts file
<Nemric> I use HDD for /var mount and I'd to fond the better way you know about saving sshd keys permanently ... any clues please ?
<Nemric> *fond -> find
<dustymabe> Nemric: you mean the SSH host keys? you can just populate them using Ignition and then new ones won't get randomly generated
lack has quit [Read error: Connection reset by peer]
<Nemric> yes, I meant host keys, but don't really want them to be stored in any ign files for security reasons (I d'ont really car about that but as I want to promote it my cmopany it's for the less mandatory ^^ ) The question of securing PXE boot and http(s) server called is quite a big subject
<dustymabe> do you have persistent storage?
<dustymabe> you could store the ssh host keys there
lack has joined #fedora-coreos
<Nemric> yes, persistent storage is on /var only
<Nemric> everything else is volatil
<Nemric> (the power of coreos) !
<dustymabe> Nemric: maybe you could store the keys in /var/ somewhere (but obviously make them only readable by root
<dustymabe> you could drop a file in /etc/ssh/sshd_config.d/ and specify `HostKey /var/foo/mykey` etc..
<dustymabe> you'd probably also want to disable sshd-keygen@.service
<Nemric> dustymabe: thanks for the tips, I'll give it a try soon ! ;)
vgoyal has quit [Quit: Leaving]
Nemric has quit [Quit: WeeChat 3.8]
bgilbert has joined #fedora-coreos
daMaestro has joined #fedora-coreos
sentenza has joined #fedora-coreos
Nemric has joined #fedora-coreos
ravanelli has quit [Remote host closed the connection]
ravanelli has joined #fedora-coreos
spresti has quit [Remote host closed the connection]
spresti has joined #fedora-coreos
Nemric has quit [Quit: WeeChat 3.8]
daMaestro has quit [Quit: Leaving]
gursewak has quit [Ping timeout: 245 seconds]
spresti has quit [Remote host closed the connection]
spresti has joined #fedora-coreos
nalind has quit [Quit: bye for now]
ravanell_ has joined #fedora-coreos
ravanelli has quit [Read error: Connection reset by peer]
spresti has quit [Remote host closed the connection]
gursewak has joined #fedora-coreos
plarsen has quit [Quit: NullPointerException!]
ravanell_ has quit [Remote host closed the connection]
ravanelli has joined #fedora-coreos
gursewak has quit [Ping timeout: 246 seconds]
gursewak has joined #fedora-coreos
daMaestro has joined #fedora-coreos
mheon has quit [Ping timeout: 250 seconds]
gursewak_ has joined #fedora-coreos
gursewak has quit [Read error: Connection reset by peer]