i am using the docker-compose to up my channel and the specification of the docker is docker version Client: Version: 20.10.12 API version: 1.41 Go version: go1.17.3 Git commit: 20.10.12-0ubuntu4 Built: Mon Mar 7 17:10:06 2022 OS/Arch: linux/amd64 Context: default Experimental: true

Server: Engine: Version: 20.10.14 API version: 1.41 (minimum version 1.12) Go version: go1.16.15 Git commit: 87a90dc Built: Thu Mar 24 17:15:03 2022 OS/Arch: linux/amd64 Experimental: false containerd: Version: v1.5.11 GitCommit: 3df54a852345ae127d1fa3092b95168e4a88e2f8 runc: Version: 1.0.3 GitCommit:
docker-init: Version: 0.19.0 GitCommit: de40ad0

the container id and images are CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 91c0a8fbcb6f hyperledger/fabric-orderer:2.1 "orderer" 13 minutes ago Up 13 minutes 0.0.0.0:7050->7050/tcp, :::7050->7050/tcp, 0.0.0.0:8443->8443/tcp, :::8443->8443/tcp orderer.example.com b36f025fdfaf hyperledger/fabric-peer:2.1 "peer node start" 14 minutes ago Up 14 minutes 7051/tcp, 0.0.0.0:9051->9051/tcp, :::9051->9051/tcp peer0.org2.example.com f683619f46bb hyperledger/fabric-peer:2.1 "peer node start" 15 minutes ago Up 15 minutes 0.0.0.0:7051->7051/tcp, :::7051->7051/tcp peer0.org1.example.com ad3cef429dfb hyperledger/fabric-orderer:2.1 "orderer" 17 minutes ago Up 17 minutes 7050/tcp, 0.0.0.0:8050->8050/tcp, :::8050->8050/tcp, 0.0.0.0:8444->8443/tcp, :::8444->8443/tcp orderer2.example.com 399a7002b7e9 hyperledger/fabric-orderer:2.1 "orderer" 17 minutes ago Up 17 minutes 7050/tcp, 0.0.0.0:9050->9050/tcp, :::9050->9050/tcp, 0.0.0.0:8445->8443/tcp, :::8445->8443/tcp orderer3.example.com 02966bfa24cb hyperledger/fabric-ca "sh -c 'fabric-ca-se…" 22 minutes ago Up 22 minutes 0.0.0.0:8054->7054/tcp, :::8054->7054/tcp ca.org2.example.com b997e28d5eef hyperledger/fabric-ca "sh -c 'fabric-ca-se…" 22 minutes ago Up 22 minutes 0.0.0.0:7054->7054/tcp, :::7054->7054/tcp ca.org1.example.com 3b9fd0dc85b3 hyperledger/fabric-peer:2.1 "peer node start" 22 minutes ago Exited (2) 4 minutes ago peer1.org1.example.com d51405c331e5 hyperledger/fabric-peer:2.1 "peer node start" 22 minutes ago Exited (2) 4 minutes ago peer1.org2.example.com d5f17f561657 hyperledger/fabric-tools:latest "/bin/bash" 20 hours ago Exited (255) 12 hours ago cli 6c1a79337a9e hyperledger/fabric-couchdb "tini -- /docker-ent…" 2 days ago Up 22 minutes 4369/tcp, 9100/tcp, 0.0.0.0:5984->5984/tcp, :::5984->5984/tcp couchdb0 8459edd281f0 hyperledger/fabric-couchdb "tini -- /docker-ent…" 2 days ago Up 22 minutes 4369/tcp, 9100/tcp, 0.0.0.0:8984->5984/tcp, :::8984->5984/tcp couchdb3 d67ea5ea4b55 hyperledger/fabric-couchdb "tini -- /docker-ent…" 2 days ago Up 22 minutes 4369/tcp, 9100/tcp, 0.0.0.0:7984->5984/tcp, :::7984->5984/tcp couchdb2 5e4aa867563e hyperledger/fabric-couchdb "tini -- /docker-ent…" 2 days ago Up 22 minutes 4369/tcp, 9100/tcp, 0.0.0.0:6984->5984/tcp, :::6984->5984/tcp couchdb1

after executing the file ./createChannel.sh, I am getting the this issue:

./createChannel.sh

2022-09-16 12:30:34.056 IST 0001 INFO [channelCmd] InitCmdFactory -> Endorser and orderer connections initialized Error: got unexpected status: SERVICE_UNAVAILABLE -- no Raft leader

the orderer in the configtx.yaml

Orderer Type: The orderer implementation to start

OrdererType: etcdraft

EtcdRaft:
    Consenters:
    - Host: orderer.example.com
      Port: 7050
      ClientTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/server.crt
      ServerTLSCert: crypto-config/ordererOrganizations/example.com/orderers/orderer.example.com/tls/server.crt

Addresses:
    - orderer.example.com:7050

# Batch Timeout: The amount of time to wait before creating a batch
BatchTimeout: 2s

# Batch Size: Controls the number of messages batched into a block
BatchSize:

    # Max Message Count: The maximum number of messages to permit in a batch
    MaxMessageCount: 10

    # Absolute Max Bytes: The absolute maximum number of bytes allowed for
    # the serialized messages in a batch.
    AbsoluteMaxBytes: 99 MB

    # Preferred Max Bytes: The preferred maximum number of bytes allowed for
    # the serialized messages in a batch. A message larger than the preferred
    # max bytes will result in a batch larger than preferred max bytes.
    PreferredMaxBytes: 512 KB