5:08 a.m.
Greetings,
I'm not sure whether the minimization effort is still going on but I
wanted to report the pitfalls I ran into moving from the fedora Docker
container to fedora-minimal.
For starters I was surprised by the absence of DNF and I had to find
by myself, I don't remember how, that MicroDNF was present instead.
So my first bit of feedback concerns the container registry. It looks a
bit... out of shape?
I get an empty page [1] when I click on the fedora-minimal container
and as of today it is by far not the only blank page. I had to keep
opening more until I found one [2] with contents. Ironically a docker
container for another container runtime...
Even when there is content, it doesn't tell much. This is where I
would hope to get the information about MicroDNF.
The other and more significant pitfall I ran into was the lack of a
timezone database. This manifests either as missing tz information
or reports of a corrupted tz database, depending on the application
I'm trying to run. Installing tzdata was a no-op, it turns out to be
installed by default but some of its contents are removed post
installation. Again, something trivial to fix, but it should be
documented on the registry:
microdnf reinstall tzdata
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.
Other than that, it seems to hum along, thanks!
Dridi
[1] https://registry.fedoraproject.org/repo/fedora-minimal/tags/
[2] https://registry.fedoraproject.org/repo/flatpak-build-base/tags/
[3] https://hub.docker.com/_/fedora
5:17 a.m.
On Mon, Jun 29, 2020 at 11:09 AM Dridi Boukelmoune
<dridi.boukelmoune(a)gmail.com> wrote:
Greetings,
I'm not sure whether the minimization effort is still going on but I
wanted to report the pitfalls I ran into moving from the fedora Docker
container to fedora-minimal.
For starters I was surprised by the absence of DNF and I had to find
by myself, I don't remember how, that MicroDNF was present instead.
So my first bit of feedback concerns the container registry. It looks a
bit... out of shape?
I get an empty page [1] when I click on the fedora-minimal container
and as of today it is by far not the only blank page. I had to keep
opening more until I found one [2] with contents. Ironically a docker
container for another container runtime...
Even when there is content, it doesn't tell much. This is where I
would hope to get the information about MicroDNF.
The other and more significant pitfall I ran into was the lack of a
timezone database. This manifests either as missing tz information
or reports of a corrupted tz database, depending on the application
I'm trying to run. Installing tzdata was a no-op, it turns out to be
installed by default but some of its contents are removed post
installation. Again, something trivial to fix, but it should be
documented on the registry:
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
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?
5:57 a.m.
> 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.
Dridi
7:32 a.m.
On Mon, 29 Jun 2020 at 12:59, Dridi Boukelmoune <dridi.boukelmoune(a)gmail.com>
wrote:
> > 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.
[0] - https://github.com/genuinetools/reg
Dridi
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)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
9:53 a.m.
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.
That can't be right, fedora-minimal is a docker/an OCI image, isn't it?
There has not been much interest in improving registry.fp.o since we
looked at moving stuff to quay.io.
Noted, being warned of known gotchas would be nice regardless of where
the images are hosted.
Dridi
2:18 a.m.
On Mon, 29 Jun 2020 at 16:55, Dridi Boukelmoune <dridi.boukelmoune(a)gmail.com>
wrote:
> 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.
That can't be right, fedora-minimal is a docker/an OCI image, isn't it?
The tag page for fedora-minimal seems to be working
https://registry.fedoraproject.org/repo/fedora-minimal/tags/. Do you have a
link of the page that is blank ?
> There has not been much interest in improving registry.fp.o since we
looked at moving stuff to quay.io.
Noted, being warned of known gotchas would be nice regardless of where
the images are hosted.
Dridi
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)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
4:22 a.m.
The tag page for fedora-minimal seems to be working
https://registry.fedoraproject.org/repo/fedora-minimal/tags/. Do you have a link of the
page that is blank ?
That's the very link from which I get a blank page, and Firefox
reports an empty resource (^U to view source).
The developer console on the other hand gives me the following warning:
The character encoding of the HTML document was not declared. The
document will render with garbled text in some browser configurations
if the document contains characters from outside the US-ASCII range.
The character encoding of the page must be declared in the document
or in the transfer protocol.
Which is logical since the content-type header doesn't give a charset and
the response body is empty.
Trying with curl -v I see the following response:
< HTTP/2 200
< date: Tue, 30 Jun 2020 09:18:47 GMT
< server: Apache
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< x-frame-options: SAMEORIGIN
< x-xss-protection: 1; mode=block
< x-content-type-options: nosniff
< referrer-policy: same-origin
< last-modified: Tue, 30 Jun 2020 08:25:07 GMT
< etag: "0-5a948e9b307cf"
< accept-ranges: bytes
< content-length: 0
< apptime: D=193
< x-fedora-proxyserver: proxy10.iad2.fedoraproject.org
< x-fedora-requestid: XvsDdwgZ9DOnVuTIdll6NQAAAAE
< content-type: text/html
Note the explicit zero content length.
HTH,
Dridi
4:12 a.m.
On Tue, Jun 30, 2020 at 09:22:45AM +0000, Dridi Boukelmoune wrote:
> The tag page for fedora-minimal seems to be working
https://registry.fedoraproject.org/repo/fedora-minimal/tags/. Do you have a link of the
page that is blank ?
I get a blank page for this one as well (and for all the other tag
pages).
This used to work though, and there hasn't been any changes in the reg
package.
Could anyone take a look in the `reg server` logs and also check if the
static content has been generated?
>That's the very link from which I get a blank page, and Firefox
>reports an empty resource (^U to view source).
>
>The developer console on the other hand gives me the following warning:
>
>> The character encoding of the HTML document was not declared. The
>> document will render with garbled text in some browser configurations
>> if the document contains characters from outside the US-ASCII range.
>> The character encoding of the page must be declared in the document
>> or in the transfer protocol.
>
>Which is logical since the content-type header doesn't give a charset and
>the response body is empty.
>
>Trying with curl -v I see the following response:
>
>< HTTP/2 200
>< date: Tue, 30 Jun 2020 09:18:47 GMT
>< server: Apache
>< strict-transport-security: max-age=31536000; includeSubDomains; preload
>< x-frame-options: SAMEORIGIN
>< x-xss-protection: 1; mode=block
>< x-content-type-options: nosniff
>< referrer-policy: same-origin
>< last-modified: Tue, 30 Jun 2020 08:25:07 GMT
>< etag: "0-5a948e9b307cf"
>< accept-ranges: bytes
>< content-length: 0
>< apptime: D=193
>< x-fedora-proxyserver: proxy10.iad2.fedoraproject.org
>< x-fedora-requestid: XvsDdwgZ9DOnVuTIdll6NQAAAAE
>< content-type: text/html
>
>Note the explicit zero content length.
>
>HTH,
>Dridi
>_______________________________________________
>devel mailing list -- devel(a)lists.fedoraproject.org
>To unsubscribe send an email to devel-leave(a)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
1:10 p.m.
On Sun, Jul 19, 2020 at 11:12:53AM +0200, Athos Ribeiro wrote:
On Tue, Jun 30, 2020 at 09:22:45AM +0000, Dridi Boukelmoune wrote:
> > The tag page for fedora-minimal seems to be working
https://registry.fedoraproject.org/repo/fedora-minimal/tags/. Do you have a link of the
page that is blank ?
I get a blank page for this one as well (and for all the other tag
pages).
This used to work though, and there hasn't been any changes in the reg
package.
Could anyone take a look in the `reg server` logs and also check if the
static content has been generated?
It has not. I did a bit of investigation, but I could not get it
working. It may be related to missing signatures after the datacenter
move.
I've filed:
https://pagure.io/fedora-infrastructure/issue/9149
with my findings.
kevin
--
> That's the very link from which I get a blank page, and Firefox
> reports an empty resource (^U to view source).
>
> The developer console on the other hand gives me the following warning:
>
> > The character encoding of the HTML document was not declared. The
> > document will render with garbled text in some browser configurations
> > if the document contains characters from outside the US-ASCII range.
> > The character encoding of the page must be declared in the document
> > or in the transfer protocol.
>
> Which is logical since the content-type header doesn't give a charset and
> the response body is empty.
>
> Trying with curl -v I see the following response:
>
> < HTTP/2 200
> < date: Tue, 30 Jun 2020 09:18:47 GMT
> < server: Apache
> < strict-transport-security: max-age=31536000; includeSubDomains; preload
> < x-frame-options: SAMEORIGIN
> < x-xss-protection: 1; mode=block
> < x-content-type-options: nosniff
> < referrer-policy: same-origin
> < last-modified: Tue, 30 Jun 2020 08:25:07 GMT
> < etag: "0-5a948e9b307cf"
> < accept-ranges: bytes
> < content-length: 0
> < apptime: D=193
> < x-fedora-proxyserver: proxy10.iad2.fedoraproject.org
> < x-fedora-requestid: XvsDdwgZ9DOnVuTIdll6NQAAAAE
> < content-type: text/html
>
> Note the explicit zero content length.
>
> HTH,
> Dridi
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)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
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)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
1371
days inactive
1391
days old
8 comments
5 participants
participants (5)
-
Athos Ribeiro -
Clement Verna -
Dridi Boukelmoune -
Kevin Fenzi -
Peter Robinson