Have issue in Docker Swarm templates. Throwing errors on config generation

[ravinayag]

Error for references 👍 ls: crypto-config/peerOrganizations/org1.example.com/ca/: No such file or directory
ls: crypto-config/peerOrganizations/org1.example.com/tlsca/: No such file or directory
ls: crypto-config/peerOrganizations/org2.example.com/ca/: No such file or directory
ls: crypto-config/peerOrganizations/org2.example.com/tlsca/: No such file or directory

Collecting the Host information for Swarm Setup

By default Orderer & Org1 will use same host, hence host & login details for swarm setup and file copy
Give your ORG_1 Hostname :testhost1
testhost1
ping: bad address 'testhost1'

testhost1 Not Pingable
Give your ORG_1 IPAddress :1.1.1.1
ping: permission denied (are you root?)
1.1.1.1 Not Pingable, Contact SYSADMIN or Check your DNS or Network Configuration

Give your ORG_2 Hostname :1.1.1.1
1.1.1.1
ping: permission denied (are you root?)

1.1.1.1 Not Pingable
Give your ORG_2 IPAddress :testhost2
ping: bad address 'testhost2'
testhost2 Not Pingable, Contact SYSADMIN or Check your DNS or Network Configuration

Updating Hostinformation for Swarm Setup

Transfering the Crypro artifacts to lab for Sync swarm Network

Considering the below

1, The Pre requestie installed i.e Docker, Fabric binary, Images, go, etc.

2, Following the same folder structure in remote host. i.e. ~/fabric-samples/

Initialising the Docker Swarm

Cleaning if any previous installs of docker swarm network from current node...
Provide a Network Interface name for swarm initialize :abc1
Docker Swarm Network Initialised
/usr/src/app/HLF/hlstartup/02_swarmstart.sh: line 243: docker: command not found
/usr/src/app/HLF/hlstartup/02_swarmstart.sh: line 247: docker: command not found
/usr/src/app/HLF/hlstartup/02_swarmstart.sh: line 250: docker: command not found
Swarm master IP:

Joining the Host: lab to Docker swarm Network

provide the username for remote host, ensure the user has admin rights: lab
Provide a Username for host : lab to login:

[ravinayag]

issue fixed and added to 0.0.5 release

[ravinayag]

fixed in 0.0.5, tested in 1.4.3 and 2.2