Fedora container not available

[pvalena]

The latest container available is from f31:

$ podman pull registry.fedoraproject.org/f33/ruby
Trying to pull registry.fedoraproject.org/f33/ruby:latest...
  manifest unknown: manifest unknown
Error: Error initializing source docker://registry.fedoraproject.org/f33/ruby:latest: Error reading manifest latest in registry.fedoraproject.org/f33/ruby: manifest unknown: manifest unknown
$ podman pull registry.fedoraproject.org/f34/ruby
Trying to pull registry.fedoraproject.org/f34/ruby:latest...
  manifest unknown: manifest unknown
Error: Error initializing source docker://registry.fedoraproject.org/f34/ruby:latest: Error reading manifest latest in registry.fedoraproject.org/f34/ruby: manifest unknown: manifest unknown
$ podman pull registry.fedoraproject.org/f35/ruby
Trying to pull registry.fedoraproject.org/f35/ruby:latest...
  manifest unknown: manifest unknown
Error: Error initializing source docker://registry.fedoraproject.org/f35/ruby:latest: Error reading manifest latest in registry.fedoraproject.org/f35/ruby: manifest unknown: manifest unknown
$ podman pull registry.fedoraproject.org/f32/ruby
Trying to pull registry.fedoraproject.org/f32/ruby:latest...
  manifest unknown: manifest unknown
Error: Error initializing source docker://registry.fedoraproject.org/f32/ruby:latest: Error reading manifest latest in registry.fedoraproject.org/f32/ruby: manifest unknown: manifest unknown
$ podman pull registry.fedoraproject.org/f31/ruby
Trying to pull registry.fedoraproject.org/f31/ruby:latest...
Getting image source signatures
Copying blob a31161543ddc [--------------------------------------] 87.6KiB / 66.2MiB
^C% 

Even though this build exists: ruby-0-18.f25docker - https://koji.fedoraproject.org/koji/buildinfo?buildID=1718180

It's not even in the container tags. Does it have to be tagged manualy, or do I have to create update in Bodhi etc.?

https://koji.fedoraproject.org/koji/builds?tagID=37069 https://koji.fedoraproject.org/koji/builds?tagID=27034 https://koji.fedoraproject.org/koji/builds?tagID=18668

TBH I'm not sure what causes this, or what is the correct workflow to fix this.

@pkubatrh @hhorak Do you know hat went wrong? Do I have to build it from f33 branch instead?

[pvalena]

I've prepared: https://src.fedoraproject.org/container/ruby/pull-request/3

[phracek]

Hi Pavel, we have created branches a couple of weeks ago.

https://pagure.io/releng/fedora-scm-requests/issue/32632 https://pagure.io/releng/fedora-scm-requests/issue/32631 https://pagure.io/releng/fedora-scm-requests/issue/32630

And because infrastructure had problems, there was no automatic sync from upstream -> downstream.

Please be patient, working on it. New upstream2downstream bot is deployed and as soon a PR is merged there should start automatic downstream sync.

[pvalena]

Great! But that doesn't explain anything of what went wrong, which is what I want to know, as I've already built an image (I'm fine with doing the sync manually, if I need it), and I want to use the container now...

[pvalena]

Btw. and I'm not fully sure how the sync would work, unless you replace the FROM in the Dockerfile for every branch. Could you clarify on that?

F.e. both f34 and f35 both have Ruby 3.0, but we don't have the Ruby 3.0/ version here yet. And both f33 and f32 have Ruby 2.7, but 2.7/Dockerfile.fedora points only to f33.

[pvalena]

@phracek what is the status of Fedora containers? :)

[phracek]

We have migrated all Fedora ruby-container into quay.io/fedora. Currently there are two repositories: https://quay.io/repository/fedora/ruby-30 and https://quay.io/repository/fedora/ruby-31. Ruby-31 has to be allowed in https://github.com/sclorg/s2i-ruby-container/blob/master/.github/workflows/build-and-push.yml. I will solve it as soon as PR #413 is merged.