Dusty Mabe
Dusty Mabe
at least `podman build` has the [ability to `retry`](https://github.com/containers/podman/blob/2b78157935b3ad45334bd8fc3649a9b8fcae6dc7/docs/source/markdown/podman-build.1.md.in#L555-L563) when pulling from the registry. I see no such options for `podman run`
xref: - https://github.com/containers/podman/issues/16973
I chimed in over in https://github.com/containers/podman/issues/19770#issuecomment-1942376610
We should be able to switch to running a `podman pull` with a `--retry` once https://github.com/containers/podman/commit/80b1e957000aec4b86f55691b8ceb0dd37308d36 lands in a FCOS release.
This ticket is meant more to be a discussion about the change. If we agree we can merge this, but let's have the conversation first.
> This is about `testing-devel` and `next-devel` builds right? correct
We also need to start re-building the jenkins container image periodically to pick up new plugin updates so we don't freeze for 6 months and potentially carry security issues. This...
I've almost talked myself into implementing lockfiles for rawhide. I feel like we need more control of that stream, but I also don't know if it's worth adding every rawhide...
> I think this is related but not the same. Yes, but if we implemented lockfiles it would solve this issue, which is why I was brought it up here...
This is mostly cosmetic issue for mechanical streams (which aren't user facing). It's a low priority.