I have just started exploring the blockchain technology. I was working around the installation part by following this tutorial.
I have created /mychain directory and docker-compose.yml. when i run the command sudo docker-compose up it starts pulling member services hyperledger/fabric-membersrvc. But after that it throws error
Pulling vp0 (hyperledger/fabric-peer:latest)...
ERROR: manifest for hyperledger/fabric-peer:latest not found
Please someone guide me on this.
Change the tag from latest to x86_64-1.0.2 in the compose file. There is no latest tag for this image. You can get all available tags on below link
https://hub.docker.com/r/hyperledger/fabric-peer/tags/
If you don't add any tags to fabric-peer, docker try to pull image with latest tag. And there is no latest tag for fabric-peer.
So you should use an available tag, see available tags here.
I had the similar issue, the problem was fabric failed to download peer binary with tag '2.2.1' and 'latest' during 'curl' command execution with following error.
Peer image getch failed:
====> hyperledger/fabric-peer:2.2.1
Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: TLS handshake timeout
Error response from daemon: No such image: hyperledger/fabric-peer:2.2.1
Error response from daemon: No such image: hyperledger/fabric-peer:2.2.1
Solution which worked for me:
Have downloaded peer 2.2.1 manually using below command
docker pull "hyperledger/fabric-peer:2.2.1"
NOTE:
"network.sh up" also throws error as it is trying to use peer binary of latest tag which is not present in docker hub. Since 2.2.1 was the latest I have created tag manually using below command.
docker image tag hyperledger/fabric-peer:2.2.1 hyperledger/fabric-peer:latest
Then it worked. You can use your version accordingly.
For HyperLedger 2.3, I found that the 'network.sh' file needs to be edited.
This file can be found under 'fabric-samples/test-network' directory.
Find the constant 'IMAGETAG' and replace its value "latest" into "2.3" or whatever your peer version is.
This constant will be referenced in all the docker-compose files.
Related
I installed (Fresh) PGO following this document : https://access.crunchydata.com/documentation/postgres-operator/v5/installation/helm/
it got deployed but the pod is in "ImagePullBackOff" state.
and "https://registry.developers.crunchydata.com/crunchydata/" is not accessible (404), saying that "This container version is no longer available".
I think the images can be found here: https://hub.docker.com/u/crunchydata
I just tried to install PGO following your link and don't have any issue. What do you have when you execute: docker pull registry.developers.crunchydata.com/crunchydata/crunchy-postgres:centos8-14.1-0 from a worker node in your cluster if your container runtime is docker .
On Raspberry Pi, I got an error when I tried to set up ODK-X Sync Endpoint.
I referred to the instruction from https://docs.odk-x.org/sync-endpoint-manual-setup/
This is the command I ran:
$ mvn clean install
The error message is as below:
Failed to execute goal io.fabric8:docker-maven-plugin:0.34.1:build (start) on project sync-endpoint-docker-swarm: Unable to pull 'tomcat:8.5' : no matching manifest for linux/arm/v7 in the manifest list entries
How can I solve this problem?
The error is fairly clear: tomcat:8.5, which sync-endpoint depends on, does not provide a manifest for the armv7 architecture. You can see this on the page for tomcat's 8.5 tag, showing that it only provides images for linux/amd64 and linux/arm64/v8.
If you need to use that Dockerfile as is and cannot change the tomcat version used, you will need to use a device with a matching architecture. If you are able to modify the Dockerfile and are willing to use a different version of tomcat, it appears that there are other tags which do support linux/arm32/v7.
I am trying to run docker file but it says this on step 1/6
'''
manifest for continuumio/anaconda3:4.9.2 not found: manifest unknown: manifest unknown
'''
This is the error it is showing
I believe you are getting such message because that tag is not available in Docker Hub. Choosing another image version may solve your problem :)
You can check the available continuumio/anaconda3 tags here https://hub.docker.com/r/continuumio/anaconda3/tags?page=1&ordering=last_updated
When trying to pull the official image for RNA-seq aligner STAR with
docker pull alexdobin/star
I got an error despite copying the Docker Pull Command as shown in the screenshot (lower right)
The error was the following:
Error response from daemon: manifest for alexdobin/star:latest not found: manifest unknown: manifest unknown
The problem is that when you don't specify the tag as part of the image name in the docker command then it is assumed that you are referring to the latest tag.
Further, as there is no image with tag latest present in the repository, you get the error as expected:
Error response from daemon: manifest for alexdobin/star:latest not found: manifest unknown: manifest unknown
Change the tag to one of the available ones and it will work as expected:
docker pull alexdobin/star:2.6.1d
You can open just the tab Tags and copy the pull command as shown in the screenshot (bottom right).
It worked just fine.
I'm attempting to compile Stygian's repack of AzerothCore as I want to add the Auction House Bot module. I have installed and set up Docker, cloned the repo and installed the module and patch, but I am receiving an error while trying to run the "./bin/acore-docker-build" command as outlined in the wiki.
I am running Windows 10 Pro
I have run the following commands:
./bin/acore-docker-generate-etc
Which appeared to work, and
./bin/acore-docker-build
Which produced the following error:
scott#DESKTOP-BGVSVR4 MINGW64 ~/Desktop/Stygian/StygianCore/Source
(master) $ ./bin/acore-docker-build unable to prepare context: unable
to evaluate symlinks in Dockerfile path: GetFileAttributesEx
C:\Users\scott\Desktop\Stygian\StygianCore\Source\docker\build: The
system cannot find the file specified. Unable to find image
'acbuild:latest' locally C:\Program
Files\Docker\Docker\Resources\bin\docker.exe: Error response from
daemon: pull access denied for acbuild, repository does not exist or
may require 'docker login'. See 'C:\Program
Files\Docker\Docker\Resources\bin\docker.exe run --help'.
Repacks are not supported by AC. You are probably using an older version of AC and not the latest.
You are getting the error:
Unable to find image 'acbuild:latest'
but in the latest version of AC, such image is baked in the same script that you're trying to run (./bin/acore-docker-build) and its Dockerfile is located in docker/build/Dockerfile.
Try to clone AC from the official repository and it will work.