title: CLI container not running Hyperledger 1.0 Not able to start (No-TLS) network
body: <p>I'm trying to follow the instructions from the <code>Hyperledger-fabricdocs Documentation Release master (May 06, 2017)</code>
  When I'm getting to the Start the network (No TLS) section and commenting out the <code>script.sh</code> in the CLI container, the following happens</p>
  
  <pre><code>$ CHANNEL_NAME=mychannel docker-compose -f docker-compose-no-tls.yaml up -d
  Creating network "e2e_default" with the default driver
  Creating orderer.example.com
  Creating peer0.org1.example.com
  Creating peer1.org1.example.com
  Creating peer0.org2.example.com
  Creating peer1.org2.example.com
  Creating cli
  $:
  </code></pre>
  
  <p>All containers get created, but immediately after creation the cli container goes down again and I'm back to the <code>e2e</code> directory. When running 
  <code>$ docker exec -it cli bash</code> from the e2e directory obviously I get the error</p>
  
  <pre><code>Error response from daemon: Container 41461c41dbecf401eab2b623d5e6930fd37f15979fd15065f87595b29e5d7b47 is not running
  </code></pre>
  
  <p>Has anyone an idea why the cli container stops running while the rest of the containers are still up (status for the cli container shows <code>Exited 1 minut ago</code>)? Is this intended and should I move into, for example, the <code>peer0.org1.example.com</code> container? Am I missing something?</p>
  
  <p>Thanks</p>