zp has quit [Read error: Connection reset by peer]
zpytela_ has joined #fedora-coreos
plarsen has quit [Quit: NullPointerException!]
jpn has joined #fedora-coreos
zpytela_ has quit [Read error: Connection reset by peer]
zpytela_ has joined #fedora-coreos
jpn has quit [Ping timeout: 268 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 268 seconds]
jpn has joined #fedora-coreos
paragan has joined #fedora-coreos
nb has quit [Quit: Ping timeout (120 seconds)]
nb has joined #fedora-coreos
bgilbert has joined #fedora-coreos
daMaestro has joined #fedora-coreos
jpn has quit [Ping timeout: 252 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 256 seconds]
daMaestro has quit [Quit: Leaving]
jpn has joined #fedora-coreos
hotbox has joined #fedora-coreos
jpn has quit [Ping timeout: 260 seconds]
bgilbert has quit [Ping timeout: 260 seconds]
bgilbert has joined #fedora-coreos
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 260 seconds]
saschagrunert has joined #fedora-coreos
bagasse has quit [Ping timeout: 268 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 260 seconds]
bagasse has joined #fedora-coreos
apiaseck has joined #fedora-coreos
Betal has quit [Quit: WeeChat 3.7.1]
<guesswhat>
Hello, question, is possible to test upstream podman on fcos? well, its easy to build podman binary, but I guess containers-common ( also fuse overlay ) package is a bigger problem...
<guesswhat>
this would probably require reboot, is there any docs how to handle this situaltion ? thanks
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 246 seconds]
jpn has joined #fedora-coreos
<travier[m]>
I should not require a reboot with the "apply-live" option.
<travier[m]>
s/./ like used in the example/
jpn has quit [Ping timeout: 272 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 268 seconds]
jpn has joined #fedora-coreos
<guesswhat>
travier[m] getting ` error: Override already exists for package 'moby-engine'` any idea?
<guesswhat>
rpm-ostree override remove moby-engine containerd runc is not needed, right?
jpn has quit [Ping timeout: 256 seconds]
jpn has joined #fedora-coreos
nalind has joined #fedora-coreos
jpn has quit [Ping timeout: 248 seconds]
mheon has joined #fedora-coreos
plarsen has joined #fedora-coreos
jpn has joined #fedora-coreos
ramcq[m] has joined #fedora-coreos
<ramcq[m]>
is there a tool in the coreos / silverblue stack that will output a "factory" (or dd, or whatever) ready disk .img given an ostree/oci image?
<travier[m]>
guesswhat: Hard to say like that. Can you make a forum post with the context / config and link it here?
<travier[m]>
Oh, looks cool! had not seen this one yet 😅). Maybe running it without an Ignition config on a loopback disk image would be the equivalent of generating an image?
<travier[m]>
* looks cool! (I had not
<walters>
yes, but in this model I don't see when you'd need raw disk images
jlebon has joined #fedora-coreos
bgilbert has joined #fedora-coreos
<travier[m]>
(ok, I need to read things again more in depth)
flokli has quit [Quit: WeeChat 3.7.1]
flokli has joined #fedora-coreos
bagasse has quit [Ping timeout: 272 seconds]
Turnikov has joined #fedora-coreos
Turnikov has quit [Ping timeout: 255 seconds]
bagasse has joined #fedora-coreos
saschagrunert has quit [Remote host closed the connection]
<nomenot>
I'm trying to add a user to the dialout group via ignition but it fails to create the user. I can grep -E '^dialout:' /usr/lib/group | sudo tee -a /etc/group and sudo usermod -aG dialout ${USER} after ignition but was hoping to set everything up without manual intervention. Any suggestions?
<nomenot>
Yes, exactly. The issue I'm running into is that dialout is an existing group even though it isn't a standard FCOS group so when I try to just list the group for my user it fails. Or if I try to create the group via the link you provided it also fails
<dustymabe>
jlebon: what's up with these `autolock` build-cosa jobs ?
<jlebon>
dustymabe: i have a temporary autolock branch on upstream cosa to make it easier for me to test it in a multi-arch setting :)
<jlebon>
i'll delete it once that PR is in
<dustymabe>
nomenot: maybe open an issue?
<dustymabe>
jlebon: is it pushing to the main quay container repo?
<jlebon>
dustymabe: yes
<dustymabe>
ok - just make sure to clean it up (as I'm sure you will)