In this article, I am going to show you how to fix a Docker error ERROR: manifest unknown: manifest unknown
fixing with the help of examples.
This typically happens when the specified image is not present either locally or in the registry you are searching.
Consider a scenario where there is an image named repository-name/image-name:v1.0.0.
In the context of the given docker-compose.yaml
file,
# Example of a docker compose version: '2' services: my-service-name: image: repository-name/image-name:v1.0.0 restart: always
I encounter the identical error when attempting to utilize a Docker image stored on Docker Hub under two circumstances:
Below is given when I input an incorrect image name:
# This is a wrong example version: '2' services: my-service-name: image: repository-name/image-wrong-name:v1.0.0 restart: always
The execution of the “docker-compose up” command results in the following error:
/usr/bin/docker-compose up -d Pulling my-service-name (repository-name/image-wrong-name:v1.0.0)... ERROR: manifest for repository-name/image-wrong-name:v1.0.0 not found: manifest unknown: manifest unknown
Alternatively, if the image version is non-existent.
# An incorrect example version: '2' services: my-service-name: image: repository-name/image-name:v1.0.1 restart: always
Encountering the same error persists:
/usr/bin/docker-compose up -d Pulling my-service-name (repository-name/image-name:v1.0.1)... ERROR: manifest for repository-name/image-name:v1.0.1 not found: manifest unknown: manifest unknown
Details regarding my environment:
The operating system platform is Linux (Ubuntu 16.04). The output of the docker version
command:
Client: Docker Engine - Community Version: 19.03.12 API version: 1.40 Go version: go1.13.10 Git commit: 48a66213fe Built: Mon Jun 22 15:45:49 2020 OS/Arch: linux/amd64 Experimental: false Server: Docker Engine - Community Engine: Version: 19.03.12 API version: 1.40 (minimum version 1.12) Go version: go1.13.10 Git commit: 48a66213fe Built: Mon Jun 22 15:44:20 2020 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.2.13 GitCommit: 7ad184331fa3e55e52b890ea95e65ba581ae3429 runc: Version: 1.0.0-rc10 GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd docker-init: Version: 0.18.0 GitCommit: fec3683
Another example:
I encountered a similar error recently, and it occurred because specifying the version is necessary. For example:
docker pull envoyproxy/envoy:v1.18.3
If you attempt without specifying the version:
docker pull envoyproxy/envoy
You will encounter the following issue:
Error response from daemon: manifest for envoyproxy/envoy:latest not found: manifest unknown: manifest unknown