# Reposync --releasever doesn't work in a rocky container **URL:** \ **Category:** Rocky Linux Help & Support\ **Created:** [June 16, 2025, 2:35pm UTC](https://forums.rockylinux.org/t/reposync-releasever-doesnt-work-in-a-rocky-container/18828 "2025-06-16T14:35:18Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![scuthber](https://avatars.discourse-cdn.com/v4/letter/s/7ab992/32.png) [@scuthber](https://forums.rockylinux.org/u/scuthber)\ **Post date:** [June 16, 2025, 2:35pm UTC](https://forums.rockylinux.org/t/reposync-releasever-doesnt-work-in-a-rocky-container/18828/1 "2025-06-16T14:35:18Z")
Just discovered this today, as reposync merrily downloaded everything 9.6 in to my 9.5 folder, meaning that I’ll have to rsync everything 9.5 from vault again! I’m guessing this is because on [https://hub.docker.com/\_/rockylinux](https://hub.docker.com/_/rockylinux) it says “The rockylinux:latest tag is intentionally missing. Please choose a major version (currently 8 or 9) tag.” This does work for Alma and RedHat, so not sure why Rocky is different? ---
**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\ **Post date:** [June 16, 2025, 5:09pm UTC](https://forums.rockylinux.org/t/reposync-releasever-doesnt-work-in-a-rocky-container/18828/2 "2025-06-16T17:09:57Z")
See this link, where I’ve mentioned before about the docker library link problem: > [@Are Docker Images no longer published?](https://forums.rockylinux.org/t/are-docker-images-no-longer-published/18391/2): > > You can do: docker pull rockylinux/rockylinux:8.10 docker pull rockylinux/rockylinux:9.5 So not sure what links you’ve been exploring on Docker Hub, but those tags above do exist. @neil would need to fix the library links for it be work in the shorthand way: docker pull rockylinux:8.10 for example. Incidently, podman deals with this better. Therefore for pulling images, rather than attempting to use the shortcut (library) link, just do: ```auto docker pull rockylinux/rockylinux: ``` replacing `` with `9.6` for example. Obviously that won’t solve your reposync problem, as that is something else entirely. But if reposyinc is using `9` instead of `9.5` or `9.6` which is symlinked to `9`, then that would explain why it overwrote what you had synced previously. ---
**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\ **Post date:** [June 16, 2025, 5:16pm UTC](https://forums.rockylinux.org/t/reposync-releasever-doesnt-work-in-a-rocky-container/18828/3 "2025-06-16T17:16:04Z")
To add on to this, mirrorlist doesn’t support the previous version either. So setting releasever will not work. This means you will need to create repo files or modify your current repo files to point to the vault in baseurl. ---
**Author:** ![scuthber](https://avatars.discourse-cdn.com/v4/letter/s/7ab992/32.png) [@scuthber](https://forums.rockylinux.org/u/scuthber)\ **Post date:** [June 17, 2025, 9:54am UTC](https://forums.rockylinux.org/t/reposync-releasever-doesnt-work-in-a-rocky-container/18828/4 "2025-06-17T09:54:41Z")
I’m using a Dockerfile, which starts: `FROM rockylinux:9` If I replace that with: `FROM rockylinux:9.5` I get: `ERROR: failed to solve: rockylinux:9.5: failed to resolve source metadata for docker.io/library/rockylinux:9.5: docker.io/library/rockylinux:9.5: not found` You’re quite correct though, replacing that with rockylinux/rockylinux:9.5 seems to work! It seems to be different from Alma/RHEL in that sense. ---
**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\ **Post date:** [June 17, 2025, 10:07am UTC](https://forums.rockylinux.org/t/reposync-releasever-doesnt-work-in-a-rocky-container/18828/5 "2025-06-17T10:07:10Z")
Replace it with: ```auto rockylinux/rockylinux:9.5 ``` to use the short name, as I already explained needs the docker library side sorting out, which is why it doesn’t work with the way you did it. Use the longer name as above. In the post I linked @neil needs to fix the docker library side for the shorter name to be used. Podman though works far better since the image side is locally, and doesn’t require changes on docker hub each time. In fact with podman, you can even create your own shortname on your servers. ---
**Author:** ![scuthber](https://avatars.discourse-cdn.com/v4/letter/s/7ab992/32.png) [@scuthber](https://forums.rockylinux.org/u/scuthber)\ **Post date:** [June 17, 2025, 10:20am UTC](https://forums.rockylinux.org/t/reposync-releasever-doesnt-work-in-a-rocky-container/18828/6 "2025-06-17T10:20:19Z")
Thanks, I did that and it works fine. The only issue I get then is that I get 404’s looking for the URL’s with reposync, which implies that --releasever _does_ work, but obviously can’t find 9.5 on the mirrors, obviously. If I edit rocky.repo and point it at `https://dl.rockylinux.org/vault/rocky/9.5/` then it all works fine. At least I should be able to fix my local mirror with that. Thanks for your help. ---
**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\ **Post date:** [June 17, 2025, 10:20am UTC](https://forums.rockylinux.org/t/reposync-releasever-doesnt-work-in-a-rocky-container/18828/7 "2025-06-17T10:20:42Z")
This is how I solve it on my Rocky server with podman instead of docker: ```auto root@vpc-ian:~# cat /etc/containers/registries.conf.d/99-rockylinux.conf [aliases] "rockylinux" = "docker.io/rockylinux/rockylinux" ``` then with podman, in Dockerfile, I can just use: ```auto FROM rockylinux:9.5 ``` ---
**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\ **Post date:** [June 17, 2025, 10:21am UTC](https://forums.rockylinux.org/t/reposync-releasever-doesnt-work-in-a-rocky-container/18828/8 "2025-06-17T10:21:50Z")
> [@scuthber](#): > > If I edit rocky.repo and point it at `https://dl.rockylinux.org/vault/rocky/9.5/` then it all works fine. At least I should be able to fix my local mirror with that. Yep, since 9.6 is now linked to 9, that’s the way you would need to resolve it to continue using 9.5. Glad you got it working 🙂 ---
**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\ **Post date:** [June 17, 2025, 10:39am UTC](https://forums.rockylinux.org/t/reposync-releasever-doesnt-work-in-a-rocky-container/18828/9 "2025-06-17T10:39:20Z")
> [@scuthber](#): > > If I edit rocky.repo and point it at `https://dl.rockylinux.org/vault/rocky/9.5/` then it all works fine. At least I should be able to fix my local mirror with that. We do know that Red Hat has not released packages for RHEL 9.5 since RHEL 9.6 was released. Therefore, there should have been many (or any) packages released for Rocky 9.5 since that date. That was the moment when I did stop mirroring 9.5 content to my local copy, so my copy “froze”. Local copy of 9.6 got its own directory. ---
**Author:** ![scuthber](https://avatars.discourse-cdn.com/v4/letter/s/7ab992/32.png) [@scuthber](https://forums.rockylinux.org/u/scuthber)\ **Post date:** [June 17, 2025, 10:50am UTC](https://forums.rockylinux.org/t/reposync-releasever-doesnt-work-in-a-rocky-container/18828/10 "2025-06-17T10:50:33Z")
That’s the plan, but unfortunately my container “contaminated” my 9.5 folder with 9.6 🙁 Not only that, but as I had --delete in there it got rid of everything 9.5. If only rsync worked through our firewall… ---
**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\ **Post date:** [August 16, 2025, 10:50am UTC](https://forums.rockylinux.org/t/reposync-releasever-doesnt-work-in-a-rocky-container/18828/11 "2025-08-16T10:50:54Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.