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
ravanelli has joined #fedora-coreos
ravanelli has quit [Remote host closed the connection]
gursewak_ has joined #fedora-coreos
mnguyen_ has joined #fedora-coreos
darknao has quit [Ping timeout: 244 seconds]
mnguyen has quit [Ping timeout: 272 seconds]
<jdoss> Are older GCP stream images removed now? I used to be able to pin a version of stable and it seems older versions are no longer available? It seems that Podman 4.1.1 updated its API in a point release and it broke the nomad-podman-driver. I'd like to roll back to 36.20220618.3.1 but it is no longer available.
<dustymabe> jdoss: how are you trying to find that image?
<dustymabe> we mark all images that aren't the latest as deprecated, but you can still use them
<jdoss> dustymabe: I used to just grab the selflink
<jdoss> server_data['server_image'] = f'https://www.googleapis.com/compute/v1/projects/fedora-coreos-cloud/global/images/fedora-coreos-{image_version}-gcp-x86-64'
<jdoss> it was the beta API tho, trying the v1 now
<jdoss> Error creating instance: googleapi: Error 400: Invalid value for field 'resource.disks[0].initializeParams.sourceImage': 'https://www.googleapis.com/compute/v1/projects/fedora-coreos-cloud/global/images/fedora-coreos-36.20220618.3.1-gcp-x86-64'. The referenced image resource cannot be found., invalid
<jdoss> No dice
<jdoss> maybe something changed in Pulumi... time to go on a snipe hunt
<dustymabe> I see it in the web interface right now
<dustymabe> Fedora, Fedora CoreOS stable, 36.20220618.3.1, x86_64 published on 2022-07-06
<jdoss> Welp, at least I know it is there. gcloud compute images describe-from-family --project "fedora-coreos-cloud" "fedora-coreos-stable" onlyu shows the latest
<jdoss> Thanks dustymabe
<dustymabe> right.. there should be a flag for showing deprecated images
<dustymabe> re-run the command with that flag
<jdoss> hmmm --help on gcloud compute images describe-from-family is not helpful
ravanelli has joined #fedora-coreos
ravanelli has quit [Remote host closed the connection]
ravanelli has joined #fedora-coreos
ravanelli has quit [Remote host closed the connection]
vgoyal has quit [Ping timeout: 276 seconds]
<jdoss> dustymabe: dots vs dashes. 36-20220618-3-1 not 36.20220618.3.1 *facepalm*
jpn has quit [Ping timeout: 244 seconds]
jpn has joined #fedora-coreos
mnguyen has joined #fedora-coreos
mnguyen_ has quit [Ping timeout: 268 seconds]
jpn has quit [Ping timeout: 268 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 244 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 255 seconds]
jpn has joined #fedora-coreos
paragan has joined #fedora-coreos
jpn has quit [Ping timeout: 240 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 244 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 272 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 272 seconds]
marmijo has joined #fedora-coreos
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 272 seconds]
mnguyen_ has joined #fedora-coreos
jpn has joined #fedora-coreos
mnguyen has quit [Ping timeout: 276 seconds]
darknao has joined #fedora-coreos
jpn has quit [Ping timeout: 272 seconds]
ksinny has joined #fedora-coreos
jcajka has joined #fedora-coreos
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 268 seconds]
phynecs has joined #fedora-coreos
flokli has quit [Quit: WeeChat 3.5]
flokli has joined #fedora-coreos
aleek has joined #fedora-coreos
aleek has left #fedora-coreos [#fedora-coreos]
phynecs has quit [Ping timeout: 276 seconds]
aleeku_ has joined #fedora-coreos
phynecs has joined #fedora-coreos
<aleeku_> hi! I'm hacking nvidia-docker image. I have coreos:35 with kernel compiled with gcc 11.2.1. But in fedora docker images (35 and 34) I can only find gcc 11.3.1 and 11.0.0 so I have version mismatch when compiling nvidia modules. How to overcome this issue?
jpn has joined #fedora-coreos
<travier[m]> aleeku_: Use the archive repo (available in CoreOS)
<travier[m]> * aleeku_: Use the archive repo (installed in Fedora CoreOS)
nb[m] has quit [Quit: You have been kicked for being idle]
nbsadminaccount- has quit [Quit: You have been kicked for being idle]
Betal has quit [Quit: WeeChat 3.6]
<travier[m]> * aleeku_: You can use the archive repo (installed in Fedora CoreOS)
<fifofonix> aleeku_: you may want to look at https://gitlab.com/nvidia/container-images/driver/-/issues/34
<fifofonix> alleku_: as of one week ago working nvidia/driver fcos images are now in NVIDIA's gitlab registry.
<aleeku_> fifofonix:yep, seen that, but I'm actually working on using nvidia-driver without docker, just unshare and chroot :)
<aleeku_> this will solve the circural dependency issue it has (docker daemon needs nvidia-docker), we will be able to enable swarm then
<fifofonix> aleeku_: In this file there is some gcc version checking (https://gitlab.com/nvidia/container-images/driver/-/blob/master/fedora/nvidia-driver).
<fifofonix> aleeku_: fwiw i'm running driver container using podman but then using it from swarm with the images that are produced. not sure what the circular dependency is.
<aleeku_> fifofonix: isn't there some issue when running podman and docker at the same time?
<fifofonix> aleeku_: it isn't recommended but for this purpose i find it stable in production over several fedora versions now. i think the issues may crop up more if you start advertising network services.
<fifofonix> fifofonix: i think it would work fine also if you ran as a systemd 'docker run' unit but i felt more comfortable security wise with a separate podman unit.
<fifofonix> fifofonix: talks to himself again. got to stop that.
ravanelli has joined #fedora-coreos
ravanelli has quit [Remote host closed the connection]
marmijo has quit [Quit: Client closed]
<aleeku_> fifofonix: thanks, I'll test podman approach then :)
jpn has quit [Ping timeout: 244 seconds]
jpn has joined #fedora-coreos
vgoyal has joined #fedora-coreos
jpn has quit [Ping timeout: 272 seconds]
ErictheITGuy[m] has left #fedora-coreos [#fedora-coreos]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 240 seconds]
jpn has joined #fedora-coreos
mnguyen has joined #fedora-coreos
mnguyen_ has quit [Ping timeout: 272 seconds]
mheon has joined #fedora-coreos
crobinso has joined #fedora-coreos
plarsen has joined #fedora-coreos
nalind has joined #fedora-coreos
crobinso has quit [Ping timeout: 272 seconds]
<jlebon> stamped and merged
ravanelli has joined #fedora-coreos
jpn has quit [Ping timeout: 268 seconds]
saqali has joined #fedora-coreos
jpn has joined #fedora-coreos
jlebon has quit [Quit: leaving]
jcajka has quit [Quit: Leaving]
<dustymabe> a few reviews to try to get the pipelines back in order:
gbsalinetti has joined #fedora-coreos
<walters> done and done
<dustymabe> walters: pushed up a followup to the first one
<dustymabe> let me look at that PR
<dustymabe> reviewed
marmijo has joined #fedora-coreos
crobinso has joined #fedora-coreos
paragan has quit [Quit: Leaving]
Betal has joined #fedora-coreos
gbsalinetti has quit [Ping timeout: 252 seconds]
gursewak_ has quit [Ping timeout: 240 seconds]
gursewak_ has joined #fedora-coreos
<dustymabe> walters: do you mind some intermediate reviews?
* dustymabe goes to find food
<walters> dustymabe: will do, mind stamping https://github.com/ostreedev/ostree/pull/2678 ?
<dustymabe> stamped
vgoyal has quit [Quit: Leaving]
ksinny has quit [Remote host closed the connection]
vgoyal has joined #fedora-coreos
jpn has quit [Ping timeout: 240 seconds]
* dustymabe also wishes prow was faster on COSA PRs -- waiting on https://github.com/coreos/coreos-assembler/pull/3006 still
<walters> yeah we can chat about this in an issue but I think we should have e.g. `/test rhcos-build` and `/test rhcos-kola` - this really can't break kola tests so there's no point running them
<walters> this also relates to our problem of "all the tests, all the time"
<dustymabe> I just wish I could see how close the prow job is to finishing
<dustymabe> total black box to me
<walters> you actually can log into the job namespace and see the pods, but agree it really needs streaming logs
<dustymabe> yeah.. also I really wish GH would send me an email when a PR I set up to automerge finally merges
<dustymabe> I think it will only do that if I tell it to send me all of my interactions (i.e. comments and all)
<walters> on a different topic, prune improvements are inbound (manually doing a fedora build for) https://github.com/ostreedev/ostree/releases/tag/v2022.5
<dustymabe> oh nice
jpn has joined #fedora-coreos
mheon has quit [Ping timeout: 268 seconds]
nalind has quit [Quit: bye]
phynecs has quit [Read error: Connection reset by peer]
jpn has quit [Ping timeout: 272 seconds]
vgoyal has quit [Quit: Leaving]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 268 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 244 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 276 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 244 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 276 seconds]