#9541 When tags at https://hub.docker.com/_/fedora will be updated to f32|latest
Closed: Fixed 3 years ago by raveit65. Opened 3 years ago by raveit65.

  • Describe the issue
    Tags at https://hub.docker.com/_/fedora are not updated to stable f32 release.
    Here the latest tag is used for old f31 release.
    When you like to change latest, 31 too latest, 32?
    We (Mate desktop) are using the fedora docker image at github for travis CI build to test our packages.
    Some build dependencies are to old from f31.
    Well, we can change our configs to use f32 directly, but we switched to latest tag to avoid to change our configs every 6 months.
    Thank you

  • When do you need this? (YYYY/MM/DD)
    When you found time....

  • When is this no longer needed or useful? (YYYY/MM/DD)

  • If we cannot complete your request, what is the impact?


Pinging @siddharthvipul1 or @cverna

I am already working on it..
f31 and f32 are failing in https://koji.fedoraproject.org/koji/packageinfo?packageID=26387

I guess for now I will just update the latest tag

Metadata Update from @mohanboddu:
- Issue tagged with: groomed, medium-gain, medium-trouble

3 years ago

Thanks but wait.
It's weird, https://hub.docker.com/_/fedora
shows latest, 32.
But a Travis (CI) build from yesterday use f31.
https://travis-ci.org/github/mate-desktop/mate-applets/jobs/704733942#L220

Status: Downloaded newer image for fedora:latest
>>> [docker inspect -f '{{.State.Running}}' mate-applets-fedora-build] <<<
>>> [docker run --name mate-applets-fedora-build --volume /home/travis/build/mate-desktop/mate-applets:/rootdir -t -d fedora:latest /bin/bash] <<<
2707a3606b61019d94ea0198cb9ee7fc9c7c5c2fca534e0c76f7d2b0b83314eb
>>> [docker exec -t mate-applets-fedora-build dnf update -y] <<<
Fedora Modular 31 - x86_64                      9.0 MB/s | 5.2 MB     00:00    
Fedora Modular 31 - x86_64 - Updates            3.2 MB/s | 4.1 MB     00:01    
Fedora 31 - x86_64 - Updates                     12 MB/s |  26 MB     00:02    
Fedora 31 - x86_64                              6.9 MB/s |  71 MB     00:10    
Last metadata expiration check: 0:00:01 ago on Fri Jul  3 17:08:35 2020.

<cut>

Upgrading:
 bash                         x86_64  5.0.17-1.fc31              updates  1.6 M
 ca-certificates              noarch  2020.2.41-1.1.fc31         updates  352 k
 cryptsetup-libs              x86_64  2.3.3-1.fc31               updates  469 k
 dbus                         x86_64  1:1.12.18-1.fc31           updates  9.5 k
 dbus-common                  noarch  1:1.12.18-1.fc31           updates   16 k
 dnf                          noarch  4.2.23-1.fc31              updates  419 k
 dnf-data                     noarch  4.2.23-1.fc31              updates   50 k
 gnupg2                       x86_64  2.2.20-2.fc31              updates  2.4 M
 gnutls                       x86_64  3.6.14-1.fc31              updates  991 k
 gpgme                        x86_64  1.13.1-7.fc31              updates  203 k

<cut>

....and so on.

And a posting at mailing list from 3 July 2020 says the same
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/T2YL6QHOXIIMI7QJXO4VPW36IXEXMFTE/#GEMYUXDKNSFVUKKLT4GF2NHW6DLQEC2U

Why?
Is this because all docker builds are failing at koji and there isn't one with a newer hash available?

Why?
Is this because all docker builds are failing at koji and there isn't one with a newer hash available?

I don't think this could be the issue since we haven't updated the hash for a while (because of data center move and then s390 build failures)

you can see that f32, latest is pointing to this file https://github.com/fedora-cloud/docker-brew-fedora/tree/d44f7abdc99edb550771c154ab81ce8f12e11172/x86_64
and it's almost 2 months old

OK, i don't know if it is an hash issue but build log at travis shows that fedora:latest is used but with f31.
Normally i would file out a report at travis and ask their for help, but the post at mailing list pointed out the same problem.

Hmm, i am not really familiar with using docker images for myself.
But i don't see a f32 directory at https://download.docker.com/linux/fedora/

https://github.com/docker-library/official-images/issues/8315
I have opened an issue on dockerhub.. will do as suggested there

This is fixed.
It was due to a bug in docker builders (they do not update images when just tags are changed like we did for latest to point to f32 from f31), for more info: https://github.com/docker-library/bashbrew/issues/8

I can confirm that the issue is fixed and fedora 32 is used with our Travis CI builds.
From today:
https://travis-ci.org/github/mate-desktop/mate-terminal/jobs/706084787#L213

Thanks a lot for fixing this.

Metadata Update from @raveit65:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata