Docker error response from daemon manifest for

It usually occurs when the image does not exist on the local machine or in the registry you are looking for.

Suppose I have an image called repository-name/image-name:v1.0.0

For the following docker-compose.yaml

    # an example of docker compose
    version: '2'
    services:
      my-service-name:
        image: repository-name/image-name:v1.0.0
        restart: always

I get the same error when trying to use a docker image stored on the dockerhub in two situations:

When I type the wrong name of the image.

    # a wrong example
    version: '2'
    services:
      my-service-name:
        image: repository-name/image-wrong-name:v1.0.0
        restart: always

The command «docker-compose up», returns the 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

Or if the version of the image doesn’t exist.

    # a wrong example
    version: '2'
    services:
      my-service-name:
        image: repository-name/image-name:v1.0.1
        restart: always

I have the same error:

    /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

Information about 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

If we disable the ‘Enable Token Authentication‘ option in Artifactory’s remote docker repository then the docker pulls will fail.

For example, as regards the following Centos image, when you perform a Docker pull:

docker pull docker.jfrog.com:8081/centos:latest
Error response from daemon: manifest for docker.jfrog.com:8081/centos:latest not found

The request.log shows: 

20190306113853|2242|REQUEST|127.0.0.1|anonymous|GET|/api/docker/docker/v2/centos/manifests/latest|HTTP/1.1|404|0

As the Docker hub only supports token-based authentication, in the UI for Arifactory’s docker-remote repository options, you»ll need to tick the Enable Token Authentication( see screenshot below) to enable the execution of Docker pulls.

Following this, the docker pull example above should work as expected.

docker pull docker.jfrog.com:8081/centos:latest

Request.log shows as below:
20190306114018|3386|REQUEST|127.0.0.1|anonymous|GET|/api/docker/docker/v2/centos/manifests/latest|HTTP/1.1|200|1721
20190306114022|3795|REQUEST|127.0.0.1|anonymous|GET|/api/docker/docker/v2/centos/manifests/sha256:365fc7f33107869dfcf2b3ba220ce0aa42e16d3f8e8b3c21d72af1ee622f0cf0|HTTP/1.1|200|529