Dusty Mabe

> Hmm, I thought we wanted to keep the property of being able to start a new build while the previous build is still finishing? ehh, I've never been too...

> > ehh, I've never been too set on that as a requirement. > > We should probably think on this a bit more and look at some numbers. It...

I wonder if there is a race condition in `podman` itself here that they would be interested to fix.

We'll be able to remove that "keep from being garbage collected" debt very soon as the fix for https://github.com/containers/podman/issues/17051 is in podman `4.5.0`, which is already in `next` and will...

@jschintag is original issue described by this ticket still an issue?

for the `too many keypairs` thing I figured out what the problem was. The web interface was telling me there were no keypairs but the CLI told me a different...

Copying from https://github.com/containers/common/pull/1216#discussion_r1110041103: > But yeah, we should probably tighten this up anyway. It wouldn't be too hard for our wrapper code to first add the known hosts entries (from...

> The harder part is reprovisioning these remote machines with the same host keys each time ([secret provisioning](https://coreos.github.io/ignition/operator-notes/#secrets) in general is an issue). Yes. This is the hard part. We...

When re-working this we could consider using a CA to establish trust too: https://jameshfisher.com/2018/03/16/how-to-create-an-ssh-certificate-authority/

> It's unlikely the cosa image we used in the x86_64 image has already been GC'ed, I believe in quay as soon as a tag gets updated the old version...