On Thu, Aug 06, 2020 at 12:02:09PM -0400, Alex Scheel wrote: > ----- Original Message ----- > > From: "Stephen John Smoogen" <smooge@xxxxxxxxx> > > To: "Development discussions related to Fedora" <devel@xxxxxxxxxxxxxxxxxxxxxxx> > > Sent: Thursday, August 6, 2020 10:55:51 AM > > Subject: Re: Respinning rawhide images every filesystem update? > > > > On Thu, 6 Aug 2020 at 10:05, Alex Scheel <ascheel@xxxxxxxxxx> wrote: > > > > > > ----- Original Message ----- > > > > From: "Stephen John Smoogen" <smooge@xxxxxxxxx> > > > > To: "Development discussions related to Fedora" > > > > <devel@xxxxxxxxxxxxxxxxxxxxxxx>, ascheel@xxxxxxxxxx > > > > Sent: Thursday, August 6, 2020 9:55:17 AM > > > > Subject: Re: Respinning rawhide images every filesystem update? > > > > > > > > On Thu, 6 Aug 2020 at 09:36, Alex Scheel <ascheel@xxxxxxxxxx> wrote: > > > > > > > > > > I'm bumping this thread. This is still broken. > > > > > > > > > > > > > Please open a ticket at > > > > https://pagure.io/fedora-infrastructure/new_issue and open new issue > > > > with an explanation of what is broken and where you are pulling from. > > > > If it is a fedora registry then infrastructure can work on a fix. If > > > > it is from docker.io or quay or elsewhere we can try to find the > > > > people who fix it and let them know. > > > > > > Opened: > > > > > > https://pagure.io/fedora-infrastructure/issue/9208 > > > > > > This was also posted to devel to hopefully get the attention of the > > > filesystem maintainer. > > > > > > > > > They seem to have ignored 1548403 since 2018. :-) > > > > > > > > > > OK so this ticket clarifies the problem because I thought this was a > > problem with the filesystem in the container image with how it is spun > > or delivered. It is instead with the package filesystem. Here is the > > ticket contents (since most people don't follow links in emails). > > There's three ways to solve this: > > 1) Make the filesystem upgrade nicely in a container, or > 2) Have the container runtime/user namespace system/... support the > type of change that upgrading the filesystem package makes, or > 3) Just respin the container image quickly whenever this happens; this > hides the problem from users without solving the problem. > > 1 isn't happening because the maintainer isn't involved. > 2 isn't happening because the container runtime maintainers punted on it. > 3 is the easiest left to accomplish. But I am confused, because as far as I can tell this is already happening. > If I had a choice, I'd be really happy with 3. I don't know what > all is involved to respin container images with a new package. I'm > sure it takes time, but I'd imagine it'd be mostly automated. The > problem gets fixed eventually anyways. It is automated. It happens every compose of rawhide. I am not sure why you are not seeing the new images. Are you pulling from registry.fedoraproject.org? kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx
