Docker Error: 'Manifest not found' – Looking for a Solution

Community Support
1

Hello,

I am getting the following error message:

docker: Error response from daemon: manifest for registry.rocket.chat/rocketchat/rocket.chat:8.0 not found: manifest unknown: manifest unknown.

It worked recently. Is it an issue on my end?

And is there a significant difference between image: registry.rocket.chat/rocketchat/rocket.chat:8.0 and image: rocket.chat:8.0?

OS: Debian 10
Docker Packages:

ii  docker-buildx-plugin            0.14.1-1~debian.10~buster     amd64        Docker Buildx cli plugin.
ii  docker-ce                       5:26.1.4-1~debian.10~buster   amd64        Docker: the open-source application container engine
ii  docker-ce-cli                   5:26.1.4-1~debian.10~buster   amd64        Docker CLI: the open-source application container engine
ii  docker-ce-rootless-extras       5:26.1.4-1~debian.10~buster   amd64        Rootless support for Docker.
ii  docker-compose-plugin           2.27.1-1~debian.10~buster     amd64        Docker Compose (V2) plugin for the Docker CLI.

DNS:

$ dig registry.rocket.chat +short
rocket-chat.docker.scarf.sh.
a390271ad366843219a41a8971aeb7c9-f3c70b7e91cf940b.elb.eu-central-1.amazonaws.com.
3.67.33.93
3.77.103.135

wget:

$ wget -O /dev/null registry.rocket.chat/rocketchat/rocket.chat
URL transformed to HTTPS due to an HSTS policy
--2026-01-27 15:47:06--  https://registry.rocket.chat/rocketchat/rocket.chat
Resolving registry.rocket.chat (registry.rocket.chat)... 3.77.103.135, 3.67.33.93
Connecting to registry.rocket.chat (registry.rocket.chat)|3.77.103.135|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2026-01-27 15:47:06 ERROR 404: Not Found.
2

Okay, my mistake. registry.rocket.chat/rocketchat/rocket.chat:8.0.1 works…