28

I'm trying to run the docker pull ibmblockchain/fabric-peer command, but I'm getting this error message:

Error response from daemon: manifest for ibmblockchain/fabric-peer:latest not found.

Is there any other way to pull this image ? Also trying to pull another images but get same error message.

AymDev
  • 6,626
  • 4
  • 29
  • 52
jitendra korde
  • 445
  • 1
  • 6
  • 11

6 Answers6

31

As you can see on below link the tag is not available

https://hub.docker.com/r/ibmblockchain/fabric-peer/tags/

You should use 1.0.1

 docker pull ibmblockchain/fabric-peer:1.0.1
Tarun Lalwani
  • 142,312
  • 9
  • 204
  • 265
  • thanks it works.but when i use **docker-compose up** command it give error. you can see below link https://stackoverflow.com/questions/45832204/module-grpc-logger-enabled-for-log-level-error-when-running-docker-compose-u – jitendra korde Aug 30 '17 at 06:48
  • That is a separate issue related to the working of image and not related to your original question – Tarun Lalwani Aug 30 '17 at 07:08
  • sorry but if you know something this will be helpful to me – jitendra korde Aug 30 '17 at 07:35
  • Post a commend on the old question or post a new one. I ran the image it booted fine for me, no error. But I didn't know how to test it – Tarun Lalwani Aug 31 '17 at 17:23
10

If you're not specifying the tag then docker will download the latest tag by default.

This error may occur if the latest tag is not attached to the latest version of the image.

To solve the problem

Example: To install Jenkins, instead of running

docker pull jenkins

I would do

docker pull jenkins:2.60.3

Thanks

1

I got the same error message when I tried to pull the image from hub.docker.com. Not this image but another. This error was related with the tag version. In my case, I push the V0.6 version and I was trying pull v0.6 version. Note that I used the upper case to write the "V" and I was trying the lower case "v". So, the tag image is really not found.

I hope this help anyone.

allicarn
  • 2,859
  • 2
  • 28
  • 47
André Carvalho
  • 927
  • 6
  • 12
1

I recently ran into this problem on windows, and realised it was because I had my docker daemon running Windows containers, this meant that the host architecture isn't a match for the architecture tags on most images. Once I switched to Linux containers all started working again.

Ceilingfish
  • 5,397
  • 4
  • 44
  • 71
0

i was also facing the same issue. Tarun's answer is correct. All you have to do is

open docker-compose.yml file and add hyperledger/fabric-peer:x86_64-1.0.2 or whichever you are pulling. close the file and run the docker-compose up command.

shinchaan
  • 136
  • 2
  • 12
0

This means the image that you are trying to pull does not exist, check the image tag or the URL that you are specifying.

Vishrant
  • 15,456
  • 11
  • 71
  • 120