Dusty Mabe
Dusty Mabe
fixed in #641
TBH it's a bit confusing upstream. See their website: https://containertoolbx.org/ They did a "rebrand" a while back to make it easier to google things, but I don't know if they...
@travier - where do we stand on this? need more discussion or someone to execute?
I feel like this is addressed by the already existing [TIP](https://github.com/coreos/fedora-coreos-docs/blob/f14e965330300fd49a730e24407472f22dfb5179/modules/ROOT/pages/provisioning-libvirt.adoc?plain=1#L13) in the docs. Did you see the TIP? Did you skip that step?
To give this a full shake I kicked off a run in staging: https://jenkins-fedora-coreos-pipeline.apps.ocp.stg.fedoraproject.org/blue/organizations/jenkins/build/detail/build/115/pipeline
> To give this a full shake I kicked off a run in staging: https://jenkins-fedora-coreos-pipeline.apps.ocp.stg.fedoraproject.org/blue/organizations/jenkins/build/detail/build/115/pipeline In that run I did a replay of a previous one where I cut out...
> For that reason alone, I'd vote to just keep using Quay.io. It's also weird because we push directly to quay for our FCOS images. Inconsistency isn't great.
> Updated with a `component` field instead of enforcing naming convention. Currently thought on `component` is to support four types of components: `[Custom Project Name] | general | bugfix |...
Maybe let's squash the two commits into one?
Will having the `example.yaml` file make things harder in the implementation? Were you planning to just ignore that file in the code? I like having it there so people can...