Why registry.opensuse is outdated to dockerhub

Hello. I’ve been wondering a few days why registry opensuse is a bit oudated (upwards of 2-3 days at most) to docker hub

It seems illogical to me, when registry opensuse org should be the official and docker hub is rate-limited.

So it would mean that people who actually use the official sources are getting an outdated snapshot of up to 3 days old and everyone is getting crammed together at hub.docker.com

https://build.opensuse.org/projects/openSUSE:Containers:Tumbleweed

I saw here that the delay seems to come from OBS, seems like there is 2 days old builds in Pulse of Tumbleweed.

So where does the builds from docker hub come from? Not from OBS?

It was quite annoying, I had a bug that had recently been fixed a snapshot, but I was forced not to use registry.opensuse - one which I had configured and added explicitly, because I thought I did myself and others a favor by using the official registry and not further hogging docker hub

https://registry.opensuse.org/cgi-bin/cooverview#opensusetumbleweed

Check it out right now

0fc192abc67c i586 20. Nov 2025 linux (386) 37MB
06a8be28a417 x86_64 21. Nov 2025 linux (amd64) 37MB
ea1e62e8ee70 armv7l 19. Nov 2025 linux (arm v7) 34MB
41ae256a8db7 aarch64 19. Nov 2025 linux (arm64 v8) 37MB
a3371525b728 ppc64le 19. Nov 2025 linux (ppc64le) 42MB
d5ee3c0de115 riscv64 22. Nov 2025 linux (riscv64) 34MB
a97a1dffc2b0 s390x 22. Nov 2025 linux (s390x) 35MB

Its 24th november? Are they really supposed to be that old?

I wonder if there’s somewhere to check what snapshots have been released?

Checked it here.
https://download.opensuse.org/history/

But still, its delayed - moreso than hub.docker by a significant amount from what it seems.

What specific part of Docker Hub are you looking at? You’ve just linked to the main page, so it’s impossible to tell what you’re comparing to.

Also, I’m looking at the opensuse registry page and seeing x86_64 and x86 at November 24:

https://hub.docker.com/r/opensuse/tumbleweed/tags

The other day I had a pkg bug in a dependency to libvips via registry.opensuse tumbleweed:latest while

  • It would install on host just fine
  • It would install via dockerhub just fine

So with the snapshot date on registry.opensuse being outdated + experience with dockerhub+baremetal host working it must be registry.opensuse being outdated.

I just think thats unfortunate, I’d like to be able to reproduce host snapshot experience in a container from official sources.

Any reason why its out of date, especially compared to dockerhub? Backlog surely can’t be that large on OBS or?

As multiple users have shown, docker hub has the latest Tumbleweed snapshots. You need to explain what you expect and what “outdated” means.

When it happens again, show the actual facts instead of telling stories.

Be careful what you wish for, because I can show the facts as soon as I am home and see the exact snapshot, the date, the package error and everything.

What about a bit of admission. You have the data right there, the snapshot does not always match up to the snapshot on history.

Why is dockerhub always up to date and official registry is not? Someone is updating dockerhub more frequently obviously.

OK, I’m going to suggest that you calm down. All Andrei is asking for is specific information rather than a narrative without actual links and details. It’s extremely difficult to diagnose something that isn’t specifically specified. It wasn’t until an hour ago that you provided specific information as to which of the 1,203 results for “opensuse” or the 151 results for “tumbleweed” on Docker Hub you were referring to. There’s no way for anyone to know anything about who is building the repo there that you’re referring to as a point of comparison, and it is absolutely reasonable to ask for clarification before attempting to help.

This is a user-to-user support forum, and you’re asking a question here that is best asked of the people who maintain the repos you’re referring to.

You’ve now provided information about which repo you’re looking at.

My speculative answer is that the two repos use different CI/CD pipelines, and probably have different automated QA processes they go through. Something may be failing in the registry.opensuse.org pipeline that isn’t failing in the Docker hub repo pipeline.

If it were me, I’d would source from the same repository if you want a reproducible result, rather than sourcing from two different repositories.

Otherwise, I would look at the build service to see who the maintainer of the repo on registry.o.o is and ask them what is causing the delay.