# No rockylinux:10 on Docker Hub

**URL:** <https://forums.rockylinux.org/t/no-rockylinux-10-on-docker-hub/20161>\
**Category:** Rocky Linux Help & Support\
**Tags:** rocky-linux-10\
**Created:** [January 22, 2026, 3:08pm UTC](https://forums.rockylinux.org/t/no-rockylinux-10-on-docker-hub/20161 "2026-01-22T15:08:08Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mdierksen](https://avatars.discourse-cdn.com/v4/letter/m/f17d59/32.png) [@mdierksen](https://forums.rockylinux.org/u/mdierksen)\
**Post date:** [January 22, 2026, 3:08pm UTC](https://forums.rockylinux.org/t/no-rockylinux-10-on-docker-hub/20161/1 "2026-01-22T15:08:08Z")

</div>

There is no rockylinux:10 on Docker Hub.

> **[rockylinux - Official Image | Docker Hub](https://hub.docker.com/_/rockylinux)**
>
> The official build of Rocky Linux.

```auto
# docker pull rockylinux:10

Error response from daemon: manifest for rockylinux:10 not found: manifest unknown: manifest unknown

```

Is there a reason for that?

---

<div class="post-metadata">

**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\
**Post date:** [January 22, 2026, 3:20pm UTC](https://forums.rockylinux.org/t/no-rockylinux-10-on-docker-hub/20161/2 "2026-01-22T15:20:16Z")

</div>

Yes, having “official docker images” is difficult to maintain (we can’t handle this ourselves). The page directs you [here](https://hub.docker.com/r/rockylinux/rockylinux).

---

<div class="post-metadata">

**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:** [January 22, 2026, 3:25pm UTC](https://forums.rockylinux.org/t/no-rockylinux-10-on-docker-hub/20161/3 "2026-01-22T15:25:14Z")

</div>

So instead of trying to use the short docker library name, use:

```bash
root@os-docker:~# docker pull rockylinux/rockylinux:10

10: Pulling from rockylinux/rockylinux
0c53e9fad032: Pull complete 
Digest: sha256:f4da504c18e7aced902f4f728cde787cd9d9b817bc639fe171026d18364dca6c
Status: Downloaded newer image for rockylinux/rockylinux:10
docker.io/rockylinux/rockylinux:10

```

---

<div class="post-metadata">

**Author:** ![mdierksen](https://avatars.discourse-cdn.com/v4/letter/m/f17d59/32.png) [@mdierksen](https://forums.rockylinux.org/u/mdierksen)\
**Post date:** [January 22, 2026, 3:51pm UTC](https://forums.rockylinux.org/t/no-rockylinux-10-on-docker-hub/20161/4 "2026-01-22T15:51:19Z")

</div>

Ah. Thank you. That works.

So rockylinux:8 and rockylinux:9 are essentially aliases and the same as rockylinux/rockylinux:8 and rockylinux/rockylinux:9?

---

<div class="post-metadata">

**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\
**Post date:** [January 29, 2026, 9:40pm UTC](https://forums.rockylinux.org/t/no-rockylinux-10-on-docker-hub/20161/5 "2026-01-29T21:40:12Z")

</div>

rockylinux/rockylinux images are the ones we directly maintain and submit and may or may not match what is in the docker official image library. The docker official library images (at the time of this writing) are completely out of date.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\
**Post date:** [March 30, 2026, 9:40pm UTC](https://forums.rockylinux.org/t/no-rockylinux-10-on-docker-hub/20161/6 "2026-03-30T21:40:17Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.