> > microdnf reinstall tzdata
>
> There's a bug about this to split out the UTC tzdata into a minimal
> tzdata so terrible hacks aren't needed to slim things down.
> https://bugzilla.redhat.com/show_bug.cgi?id=1722233
I'll CC myself to this bug but it doesn't look like anything will happen soon.
> > By comparison dockerhub, from which I used to pull fedora images
> > before moving to fedora-minimal has a nice landing page [3] and
> > maybe it's also failing to document pitfalls but so far the base image
> > never surprised me.
>
> Anything that's particularly stripped back will always be a compromise
> of size vs functionality, if the stacked image did what you already
> needed why change?
I needed to deploy more services on a very constrained box, and this has
given me enough headroom not to worry for a while. Compromise is fine,
but finding out through trial&error is needlessly tedious. Unless of course
I missed the red tape with "here be dragons", in which case it would have
been totally on me and that's where I think Fedora's container registry
could be improved.
I'm wondering whether container pages went blank because something
went missing during the recent data center move.
The blank pages are flatpaks. We are using the same registry for containers and flatpaks and the upstream project[0] used for registry.fp.o does not support flatpaks so the page is just blank.
There has not been much interest in improving registry.fp.o since we looked at moving stuff to
quay.io.
Dridi
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
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@lists.fedoraproject.org