[Help] Peer manager is unable to connect to peers in a private network

I've also asked this question here, but what are the main reasons the peer manager is unable to connect to peers. My setup is a debian 8 jessie machine running on a virtual machine, on VirtualBox with NAT settings.

Also, in the Running a private network article, the following docker_compose.yml file is used:
bootstrap:
  image: ethereum/client-python
  container_name: bootstrap
  entrypoint: /usr/local/bin/pyethapp
  command: "-c eth.network_id=1337 -c node.privkey_hex=091bd6067cb4612df85d9c1ff85cc47f259ced4d4cd99816b14f35650f59c322 -b 'enode://288b97262895b1c7ec61cf314c2e2004407d0a5dc77566877aad1f2a36659c8b6[email protected]localhost:30303' run --fake"
  ports:
    - 127.0.0.1:30304:30303
    - 127.0.0.1:30304:30303/udp

eth:
  image: ethereum/client-python
  links: 
    - bootstrap
  entrypoint: /usr/local/bin/pyethapp
  command: "-c eth.network_id=1337 -b 'enode://288b97262895b1c7ec61cf314c2e2004407d0a5dc77566877aad1f2a36659c8b6[email protected]bootstrap:30303' run --fake"

miner:
  image: ethereum/client-python
  links: 
    - bootstrap
  entrypoint: /usr/local/bin/pyethapp
  command: "-c eth.network_id=1337 -b 'enode://288b97262895b1c7ec61cf314c2e2004407d0a5dc77566877aad1f2a36659c8b6[email protected]bootstrap:30303' -m 50 run --fake"

debug:
  image: ethereum/client-python
  container_name: debug
  links: 
    - bootstrap
  entrypoint: /usr/local/bin/pyethapp
  command: "-c eth.network_id=1337 -b 'enode://288b97262895b1c7ec61cf314c2e2004407d0a5dc77566877aad1f2a36659c8b6[email protected]bootstrap:30303' -l :debug,p2p:info run --fake"
My understanding of this setup is not clear; it is mentioned that the bootstrap node acts as a bridge between the remaining nodes and the host machine (implying that all nodes use the bootstrap node to connect to another network?).

Where is the block chain stored in this setup? the bootstrap node or all nodes have a copy of it?

If this is meant to be a private (isolated from any other ethereum external resource) network, why does peer synchronization fail (all peers run on the same host)?

Also, when showing the logs there appear to be more than four nodes present and running on the network. Shouldn't there only be four as specified in the configuration file (docker-compose.yml)?
Sign In or Register to comment.