Duplicate mount points

[cmoro-deusto]

On first step of One Organisation Network, I get a "Duplicate mount points" error from docker-compose.

Steps to reproduce

• Clone the project (error happens in master and stable branches)
• Set up env variables export ORG=org1 DOMAIN=example.com
• Launch orderer docker-compose -f docker-compose-orderer.yaml up -d

Apparently it hangs, but launching with verbose reveals the problem:

docker-compose -f docker-compose-orderer.yaml --verbose up -d
compose.config.config.find: Using configuration files: ./docker-compose-orderer.yaml
ERROR: compose.cli.main.main: Duplicate mount points: [/home/dordoka/Code/hlf/fabric-starter/crypto-config/hosts_orderer:/etc/hosts:rw, /home/dordoka/Code/hlf/fabric-starter/crypto-config/hosts:/etc/hosts:rw]

Versions Information

docker version

Client: Docker Engine - Community
 Version:           19.03.5
 API version:       1.40
 Go version:        go1.12.12
 Git commit:        633a0ea838
 Built:             Wed Nov 13 07:29:52 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.5
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.12
  Git commit:       633a0ea838
  Built:            Wed Nov 13 07:28:22 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.10
  GitCommit:        b34a5c8af56e510852c35414db4c1f4fa6172339
 runc:
  Version:          1.0.0-rc8+dev
  GitCommit:        3e425f80a8c931f88e6d94a8c831b9d5aa481657
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

docker-compose version

docker-compose version 1.25.0-rc4, build 8f3c9c58
docker-py version: 4.1.0
CPython version: 3.7.4
OpenSSL version: OpenSSL 1.1.0l  10 Sep 2019

[selvaraman]

I am also facing same problem. I think this is because we are having two mount at same place.

   volumes:
      - ./crypto-config/hosts_orderer:/etc/hosts
      - ./crypto-config/hosts:/etc/hosts

Any one know fix for this?

[LeonidLe]

fixed this in the stable branch, but can't reproduce in master