-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should we update and regularly rebuild the images or not? #5
Comments
I'd perfer weekly rebuilds for Arch as we are dealing with work containers. |
Any particular reason for weekly rebuilds? Do you re-create one every week? Then if that's the case do you re-install all your tools there every time? Then I'd say that maybe you're better served by having your own container build from another repo on top of this one. I have mine in https://github.com/travier/quay-containerfiles/tree/main/toolbox for example that builds on top of the Fedora one. I would say that the target for those images is people that create an image and update it over time instead of re-creating it all the time. |
Packages update fast in Arch. If you create a new container at the tailend of the month then a lot of those packages are going to be old. It's better to use |
OK, let's do weekly rebuilt. I hope we'll have enough built minutes. |
The same reasoning for periodical rebuilds can also apply to Fedora Rawhide. |
Agree that Rawhide should be rebuilt regularly. Is this not the case right now? |
Note that most of the images here do not update the packages. I'm looking at that in #20. |
Looks like I read https://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions incorrectly and actions minutes are free and unlimited for public projects. I will turn builds on in PRs. |
All Fedora Toolbx images are being rebuilt regularly. I mainly mentioned it to support the need for Arch Linux images to be rebuilt regularly. |
I think Ubuntu images should be rebuilt bi-weekly but at least once a month. |
Then they need some work like I did in 52a51d5 for the CentOS ones as right now they don't update at all. |
Well, they do get updated but only if the base image is updated. |
Make sure to not re-use cached layers to always fully update the image every time we rebuilt it. See: #5
#41 should close this one. |
See discussion in #41, we'll not update Debian & Ubuntu images. |
Just to be clear ... These days, since the Fedora 39 development cycle, the Currently, the built-in |
Right now, the Containerfiles do not update the packages in the image.
We have two options:
Note: This discussion apply to Arch Linux too but we need to keep it updated monthly at miminum.
The text was updated successfully, but these errors were encountered: