Hey all, I am using docker and pulled the latest version of rawhide to use interactively. Sitting in the container I ran `dnf -y update` and got: Config error: Parsing file "/etc/dnf/dnf.conf" failed: Parsing file '/etc/dnf/dnf.conf' failed: IniParser: Missing section header at line 1 I stopped the container, deleted it, deleted the image, tried to pull a fresh instance and got exactly the same issue. Suffice to say this makes the container unusable. What's the protocol for informing the powers-that-be about this issue? Ron

Seems a bit disappointing. I’ve been searching but cannot find any info on configuring docker to use Fedora’s repo so I could just ignore the issue altogether. :)

Yep, that worked, thanks! For folks searching similar info later, I ran: docker pull registry.fedoraproject.org/fedora:rawhide On 6 Jun 2023, at 8:34, David Schwörer wrote: Seems a bit disappointing. I’ve been searching but cannot find any info on configuring docker to use Fedora’s repo so I could just ignore the issue altogether. :) You should be able to use a full url: podman pull registry.fedoraproject.org/fedora:rawhide podman pull quay.io/fedora/fedora:rawhide Same should be true for docker, but I haven't tested. ------------------------------ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue _______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Once upon a time, Clement Verna <cverna(a)fedoraproject.org&gt; said: > Once https://github.com/docker-library/official-images/pull/14789 merges, > the rawhide image on the DockerHub should be fixed too :-) So... if it takes a manual process (including opening a PR), does it really make sense to put Rawhide images on Dockerhub?

On Wed, 7 Jun 2023 at 19:15, Kevin Fenzi <kevin(a)scrye.com&gt; wrote: > > On Tue, Jun 06, 2023 at 12:30:56PM -0500, Chris Adams wrote: > > Once upon a time, Clement Verna <cverna(a)fedoraproject.org&gt; said: > > > Once https://github.com/docker-library/official-images/pull/14789 merges, > > > the rawhide image on the DockerHub should be fixed too :-) > > > > So... if it takes a manual process (including opening a PR), does it > > really make sense to put Rawhide images on Dockerhub? > > Sadly, lots of people look there, but yeah... it's not great. Yeah, basically, because $VISIBILITY. Anyway this looks like something that could be easily automated via GH Actions.

On 6/7/23 13:31, Kevin Fenzi wrote: > On Wed, Jun 07, 2023 at 07:19:32PM +0200, Iñaki Ucar wrote: > > On Wed, 7 Jun 2023 at 19:15, Kevin Fenzi <kevin(a)scrye.com&gt; wrote: > > > On Tue, Jun 06, 2023 at 12:30:56PM -0500, Chris Adams wrote: > > > > Once upon a time, Clement Verna <cverna(a)fedoraproject.org&gt; said: > > > > > Once https://github.com/docker-library/official-images/pull/14789 merges, > > > > > the rawhide image on the DockerHub should be fixed too :-) > > > > So... if it takes a manual process (including opening a PR), does it > > > > really make sense to put Rawhide images on Dockerhub? > > > Sadly, lots of people look there, but yeah... it's not great. > > Yeah, basically, because $VISIBILITY. Anyway this looks like something > > that could be easily automated via GH Actions. > Any automation there would probibly need buy-in from docker folks, > because if we filed a automated PR every day and a docker human had to > review/merge it, they might not think thats a good way to spend their > time. > > kevin > If people would just use Podman they would not have this issue.

Il 07/06/23 21:10, Adam Williamson ha scritto: > On Wed, 2023-06-07 at 14:55 -0400, Daniel Walsh wrote: >> On 6/7/23 13:31, Kevin Fenzi wrote: >>> On Wed, Jun 07, 2023 at 07:19:32PM +0200, Iñaki Ucar wrote: >>>> On Wed, 7 Jun 2023 at 19:15, Kevin Fenzi <kevin(a)scrye.com&gt; wrote: >>>>> On Tue, Jun 06, 2023 at 12:30:56PM -0500, Chris Adams wrote: >>>>>> Once upon a time, Clement Verna <cverna(a)fedoraproject.org&gt; said: >>>>>>> Once https://github.com/docker-library/official-images/pull/14789 merges, >>>>>>> the rawhide image on the DockerHub should be fixed too :-) >>>>>> So... if it takes a manual process (including opening a PR), does it >>>>>> really make sense to put Rawhide images on Dockerhub? >>>>> Sadly, lots of people look there, but yeah... it's not great. >>>> Yeah, basically, because $VISIBILITY. Anyway this looks like something >>>> that could be easily automated via GH Actions. >>> Any automation there would probibly need buy-in from docker folks, >>> because if we filed a automated PR every day and a docker human had to >>> review/merge it, they might not think thats a good way to spend their >>> time. >>> >>> kevin >>> >> If people would just use Podman they would not have this issue. >> > The Bodhi CI (one of the affected cases) seems to actually support both > docker and podman, but default to docker. Not sure why, I guess Mattia > could say. No idea... the CI stuff was present before I started messing with Bodhi. I think it was set up by CPE folks. But... how does using podman would overcome the issue? As far as I know, `docker` command in fedora is just a wrapper which runs podman. Doesn't podman uses the same dockerfiles? Or maybe podman understands the 'FROM fedora:rawhide' differently than docker (doesn't point to docker hub as default)?