Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker-compose -f single-peer-ca.yaml up failed #30

Open
emilyling opened this issue Jun 14, 2017 · 5 comments
Open

docker-compose -f single-peer-ca.yaml up failed #30

emilyling opened this issue Jun 14, 2017 · 5 comments

Comments

@emilyling
Copy link

OS:Red Hat Enterprise Linux Server release 7.3 x86_64
docker version:
Client:
Version: 17.03.1-ee-3
API version: 1.27
Go version: go1.7.5
Git commit: 3fcee33
Built: Thu Mar 30 20:03:25 2017
OS/Arch: linux/amd64

Server:
Version: 17.03.1-ee-3
API version: 1.27 (minimum version 1.12)
Go version: go1.7.5
Git commit: 3fcee33
Built: Thu Mar 30 20:03:25 2017
OS/Arch: linux/amd64
Experimental: false

docker compose version:
docker-compose version 1.13.0, build 1719ceb
docker-py version: 2.2.1
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.0.1t 3 May 2016

peer-secure-base.yaml:
version: '2'
services:
peer-secure-base:
volumes:
- /var/run/docker.sock:/var/run/docker.sock
environment:
- CORE_PEER_ID=vp0
- CORE_PEER_DISCOVERY_PERIOD=300s
- CORE_PEER_DISCOVERY_TOUCHPERIOD=301s
- CORE_PEER_ADDRESSAUTODETECT=true
- CORE_VM_ENDPOINT=http://172.17.0.1:2375
- CORE_LOGGING_LEVEL=DEBUG
- CORE_PEER_PKI_ECA_PADDR=membersrvc:7054
- CORE_PEER_PKI_TCA_PADDR=membersrvc:7054
- CORE_PEER_PKI_TLSCA_PADDR=membersrvc:7054
- CORE_SECURITY_ENABLED=true
command: sh -c "sleep 10; peer node start"
single-peer-ca.yaml:
version: '2'
services:
baseimage:
build: ./baseimage
image: hyperledger/fabric-baseimage:latest

membersrvc:
image: ibmblockchain/fabric-membersrvc:${ARCH_TAG}
extends:
file: base/membersrvc.yaml
service: membersrvc

vp0:
image: ibmblockchain/fabric-peer:${ARCH_TAG}
extends:
file: base/peer-secure-base.yaml
service: peer-secure-base
ports:
- "7050:7050"
- "7051:7051"
- "7053:7053"
environment:
- CORE_PEER_ID=vp0
- CORE_SECURITY_ENROLLID=vp
- CORE_SECURITY_ENROLLSECRET=f3489fy98ghf
links:
- membersrvc

Command:
docker-compose -f single-peer-ca.yaml up
Error details:
Creating dockercompose_baseimage_1 ...
Creating dockercompose_membersrvc_1 ...
Creating dockercompose_baseimage_1
Creating dockercompose_baseimage_1 ... error

ERROR: for dockercompose_baseimage_1 Cannot create container for service baseimage: mkdir /var/lib/docker/overlay/48e7462e11d3200a59b3290a8132edf134ada67f2f87ed6e64e0e1a9c904e52c-init/merged/dev/shCreating dockercompose_membersrvc_1 ... error

ERROR: for dockercompose_membersrvc_1 Cannot create container for service membersrvc: mkdir /var/lib/docker/overlay/755edffb61f6079753696073de4e4ef8fcb5d6863bcd96f5c12a60b6c7ad568e-init/merged/dev/shm: invalid argument

ERROR: for membersrvc Cannot create container for service membersrvc: mkdir /var/lib/docker/overlay/755edffb61f6079753696073de4e4ef8fcb5d6863bcd96f5c12a60b6c7ad568e-init/merged/dev/shm: invalid argument

ERROR: for baseimage Cannot create container for service baseimage: mkdir /var/lib/docker/overlay/48e7462e11d3200a59b3290a8132edf134ada67f2f87ed6e64e0e1a9c904e52c-init/merged/dev/shm: invalid argument
ERROR: Encountered errors while bringing up the project.
Could you help to check the issue?
I have the images as below:
ibmblockchain/fabric-membersrvc x86_64-0.6.1-preview b3654d32e4f9 7 months ago 1.42 GB
hyperledger/fabric-baseimage latest 21cb00fb27f4 7 months ago 1.42 GB
ibmblockchain/fabric-peer x86_64-0.6.1-preview 21cb00fb27f4 7 months ago 1.42 GB
At the same time I have kubernates master in it.
I have tried to delete the images and do the command:
docker-compose -f single-peer-ca.yaml up
again, the error still happen.
For the command:
docker-compose -f four-peer-ca.yaml up
has the same error.

@mrshah-at-ibm
Copy link
Contributor

@emilyling does the user running the docker command have permissions on /var/lib/docker folder?

@emilyling
Copy link
Author

yes I have the permission.
I use root to run docker command

@emilyling
Copy link
Author

@mrshah-at-ibm Do you have any idea about this? Thanks for your great help.
Thank you very much!

@mrshah-at-ibm
Copy link
Contributor

@emilyling I don't have much information, but you should check if docker daemon has permissions to the folder.

@emilyling
Copy link
Author

emilyling commented Jun 21, 2017

#docker info
Containers: 10
Running: 10
Paused: 0
Stopped: 0
Images: 13
Server Version: 17.03.1-ee-3
Storage Driver: overlay
Backing Filesystem: extfs
#ll /var/lib/docker/
drwx------ 143 root root 20480 Jun 21 00:53 overlay
I run all the command using root.
I think docker has the permission for this folder:/var/lib/docker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants