matti
November 21, 2025, 7:59am
1
Pulling Rocket.Chat 7.11.1 image fails.
[‘podman’, ‘–version’, ‘’]
reetp
November 21, 2025, 12:26pm
2
No idea but you should be using the latest version of 7.11. which is 7.11.2 as of today.
reetp
November 23, 2025, 11:47am
3
I think there were some CI failures.
Please try again and let us know.
matti
November 24, 2025, 8:30am
4
I got the same error for 7.11.1.
For 7.11.2, I got another error.
[‘podman’, ‘–version’, ‘’]using podman version: 4.3.1podman pull registry.rocket.chat/rocketchat/rocket.chat:7.11.2Trying to pull registry.rocket.chat/rocketchat/rocket.chat:7.11.2…Error: initializing source docker://registry.rocket.chat/rocketchat/rocket.chat:7.11.2: reading manifest 7.11.2 in registry.rocket.chat/rocketchat/rocket.chat: manifest unknown: manifest unknownexit code: 125
reetp
November 24, 2025, 9:50am
5
Msnifest failure is a fail in their CI.
I will ask.
matti
November 25, 2025, 12:56pm
6
Today I got the 500 Internal Server Error with version 7.11.2 too.
['podman', '--version', '']
using podman version: 4.3.1
podman pull registry.rocket.chat/rocketchat/rocket.chat:7.11.2
Trying to pull registry.rocket.chat/rocketchat/rocket.chat:7.11.2...
Getting image source signatures
Copying blob ba4caef5715c skipped: already exists
Copying blob 0a9a5dfd008f skipped: already exists
Copying blob 82bea49235a6 skipped: already exists
Copying blob 0c6d1cca3259 skipped: already exists
Copying blob f4703591a7b4 [--------------------------------------] 0.0b / 321.9MiB
Copying blob 4f4fb700ef54 skipped: already exists
Copying blob b15fa935a955 [--------------------------------------] 0.0b / 133.3MiB
Copying blob 7ee4e2743961 [--------------------------------------] 0.0b / 37.6MiB
Copying blob cd46a50784d9 [--------------------------------------] 0.0b / 24.6KiB
Error: reading blob sha256:b15fa935a9557c56f33bdff5b3d2f68da4b047e6f63c1afb81d0fe71c7d20508: Error fetching blob: invalid status code from registry 500 (Internal Server Error)
exit code: 125
reetp
November 27, 2025, 11:30am
7
I just pulled 7.11.2 without issues.
registry.rocket.chat/rocketchat/rocket.chat 7.11.2 14b0da5d70f6 2 days ago 2.02GB
7.10.5 is still broken.
matti
November 27, 2025, 11:34am
8
I still got the 500 Internal Server Error when I tried to pull version 7.11.2.
reetp
November 27, 2025, 11:49am
9
In that case you have another issue.
I literally tried this just now to check.
docker compose pull rocketchat
[+] Pulling 10/10
✔ rocketchat Pulled 56.7s
✔ 0a9a5dfd008f Already exists 0.0s
✔ ba4caef5715c Already exists 0.0s
✔ 0c6d1cca3259 Already exists 0.0s
✔ 82bea49235a6 Already exists 0.0s
✔ b15fa935a955 Pull complete 6.9s
✔ f4703591a7b4 Pull complete 52.7s
✔ 7ee4e2743961 Pull complete 55.4s
✔ cd46a50784d9 Pull complete 55.4s
✔ 4f4fb700ef54 Pull complete 55.4s
docker images
REPOSITORY TAG IMAGE ID CREATED SIZEregistry.rocket.chat/rocketchat/rocket.chat 7.11.2 14b0da5d70f6 2 days ago 2.02GBregistry.rocket.chat/rocketchat/rocket.chat 7.12.2 289784fb6257 4 days ago 2.06GB
You might want to clear all your docker cache completely.
eg
docker volume rm $(docker volume ls -q)
docker system prune -af
matti
November 27, 2025, 12:48pm
10
I don’t have any podman volumes. podman system prune -af did not fix the error.
reetp
November 27, 2025, 1:25pm
11
So you have some other issue which you need to resolve.
We don’t have enough information to help.
I have literally just installed podman on a clean Rocky v8 VM I had and very quickly hacked a config and it works out of the box.
I followed the docs like this:
dnf install podman podman-compose git
mkdir git
cd git
git clone --depth 1
cd rocketchat-compose
cp .env.example .env
nano .env
{Set Release to 7.11.2}
podman-compose -f compose.database.yml -f compose.yml up -d
That was it.
I suggest you look at your network for start.
Then you need to tell us all about your OS, network podman setup, configs etc. because you have told us nothing apart from ‘it doesn’t work’.
See this on how to report issues effectively.
Information that support or devs will require
