On 8/30/19 9:36 AM, Kamil Paral wrote: > On Thu, Aug 29, 2019 at 4:33 PM Dusty Mabe <dusty@xxxxxxxxxxxxx <mailto:dusty@xxxxxxxxxxxxx>> wrote: > > I don't know the formal process for proposal but here is a shot at a bare minimum > start for trying to add containers to the existing release criteria. This is a suggestion > after we found podman can't pull containers from a registry in f31 [1]. > > New section for Containers and Container tools: > > - A Fedora system can install the podman container runtime > - The podman container runtime can pull/run a container from Fedora's registry as root > - The podman container runtime can pull/run a container from Fedora's registry as a non-root user > > As for the container I'd suggest the previous fedora release's container (i.e. f30 for f31). > > > Correct me if I'm not thinking straight, but Fedora containers are not release blocking right now. If we require that latest stable fedora container must be pulled and run correctly, we will corner ourselves if the container is broken. Because we will block the release on a compose artifact which is itself not release blocking. So unless I'm talking nonsense, it might be better to specify "any container" (and recommend to test with latest stable fedora container). Your suggestion is exactly my suggestion above where I say: "As for the container I'd suggest the previous fedora release's container (i.e. f30 for f31)." Dusty _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
